I've had the same issue. It's one of two things. Either upnp is not activated properlyor working properly on the Ubiquiti or the IP you have in the Fios Routers DMZ is not correct.

Dmz is def correct. And idk how upnp would have changed. It’s a modified file that sits on the cloud keys sd card but I’ll check.

I haven't used Ubiquity. I just did a quick search of the USG. If what I read was correct there is no settings for upnp in the GUI and you have to make those changes in the json file, is that right? If so you also have to re-provision after making those changes or else they are just in the cloud and not in effect in the device was that done properly?

You can ssh into it and drop the file with the added config into the directory on the cloud key itself. That’s what I did and it resulted it in working until I put it behind the second router.

So, when the Ubiquity was the only router, you were able to choose "connect Remotely" and get into the Wattbox via OVRC when you were logging in from an entirely different network? Just making sure you weren't on the same network and choose connect local, since UPNP would not be needed.

If you go into Ovrc and go to the wattbox and click on the gear icon and then choose info, what is the info showing under Network Info: Don't post the WAN IP but you can post:

LAN IP:
Subnet Mask
Device Gateway
DNS Server 1

Curious to see what is getting reported to OVRC. Also, did you verify that infact the WAN IP shown is correct (i.e. what the Fios router is pulling and should also be the same as going to whatismyip.com on site)

I have a client with dual DSL modems from MyFrontier. Not sure if you could add a dumb modem onto the service and feed your router.

Once I enabled upnp yes. It finally worked then when I selected Remote. I could drop my wifi connection off the phone. Use cellular and bam it would load my ip from service provider and the random port it would generate after the ip and it would load the gui on the webpage. Then I took it to clients who has Verizon, I have time Warner, put it behind his router in the dmz and it will no longer work.

Secondary dns 8.8.4.4

The wan ip it lists is correct.

My usg gateway obviously has 192.168.1.1 listed as its gateway with its assigned static wan ip being192.168.1.2 LAN side is 192.168.100.1

Im more concerned with why the heck the ubiquiti smtp won’t work (yet wattbox does wtf?) then I am with why the wattbox gui won’t load. It’s kind of set it once and forget it anyways. I don’t really need to log into that portal remotely. The ovrc app gives me enough control. Auto reboot works fine as it does ping servers fine, I can manually reboot outlets. Smtp notifications work. So whatever. Besides I think if I setup dynamic dns on it it will work remotely from what I read in their documentation. I can set it for a static port and I’m guessing it’s gonna work. It’s probably a UPNP issue or double nat problems from crossing two routers f’ing up the remote connect. Googling issues of double nat I see this kind of stuff mentioned as downsides.

Again what I really would like to figure out is how to get smtp notifications working on the ubiquiti stuff again. All my config for my mail server is spot on. It authenticates fine. Just fails sending mail. Yet the wattbox does it no problem. Figure that one out.

As far as SMTP, could be issues with how SMTP is done, authentication etc on the Ubiquity vs the Wattbox. As far as the wattbox, I just leave the notifications handled by OVRC vs the wattbox itself.

I know you said you were able to web connect in before when the Ubiquity was on your network. However, were you even able to webconnect remotely to the Wattbox at your clients house when everything was hooked up to just the Fios router (pre- Ubiquity ?). Just making sure there isn't an issue with the wattbox at your clients house.

Otherwise I am stumped. I assume you rebooted both the Fios router and your Ubiquity after finally getting the Lan configured correctly? My guess is something is messed up with your config of the Ubiquity somehow. Maybe the SMTP issue is related.

I know you had this up and working at your house. If you just had the Ubiquity pulling its WAN IP via DHCP, it probably would have been pretty much plug and play with just 2 quick configs on the Fios router when you brought your Ubiquity over to the job. (I.e. setting a DHCP reservation and the DMZ). No need then to fool with anything else. Since I don;t know Ubiquity and cloudkey I don;t know if anything else would of had to have been re-provisioned when moving but wouldn;t think so.

You had issues and problems initially at the clients house when trying to configure the LAN and WAN properly. Lost access, etc and thus who knows if something was messed up.

IMHO, I would probably do 2 things at the clients house. For one, I would change to DHCP on the wan side of the Ubiquity. Thus, it pulls its network info from the Fios. Everything on Lan side seems fine. Then would reset the fios router to its default settings, thus closing the DMZ, removing any ports opened manually/automatically, etc. This way you know its clean. Verify all setting reverted and a true reset was done. Then go in and do the DHCP reservation in the Fios Router for the Ubiquity, setting it to 192.168.1.2. Then do the DMZ process again putting 192.168.1.2 as the DMZ address. Reboot your Ubiquity and verify from a computer or phone connected to the Ubiquity that its WAN IP is 192.168.1.2. Then turn off wifi on phone and try doing a web connect via ovrc.

If its not working I would then take you Ubiquity out and bring it back home and see if it still works properly. i.e. can web connect and STMP notifications send. If not there is a config issue or something and you need to get it working in your house and once working, should then be OK and can bring it back over and you should just be able to plug it back in and be up. Test it and see if you can web connect and if smtp notifications still work.

The smtp config isn’t much more then email port and server name. It’s def correct. Who knows.

set the watt box up for dns. I can now access the web gui remotely thru that with a static port forwarded.

rti also sends messages via smtp. so this only leaves the last issue with ubiquiti not sending mail. maybe its their current version of firmware who knows.

This seems to confirm my suspicions that there is an issue with Upnp on your Ubiquity.

ya i went back in and the file was deleted. the config.properties file. so i readied it. still didn't work this time. so i said ya know what f it. have enough time invested in it. So setup the dynamic dns and onto the next job.

So I have this take over installation where there is only the Fios Router. Normally I would just use my own router behind the Fios router and connect all equipment to that as described in this thread and all of the cable boxes would be connected via Moca to the Verizon box on a separate network.

There is a whole bunch of WAP's in this house and there are areas where coverage sucks. No way to run new wiring, so I am limited to area's where there were ethernet lines run. The Master Bedroom has no ethernet but had a Coax line w/ a cable box. So at first I had thought about using a Moca Adapter. All is fine if I leave the Fios router as the sole router. If I wanted to add my own vpn router then I can't just use a Moca extender on that coax line cause this would be on a different network. I could use a pair of extenders and then just al of the cable boxes then connected to my router, sitting in the DMZ of the Fios router. But, guessing that won't work for the cable boxes without additional port forwarding? Or will it since the fits router is still in the mix, since its not eliminated.