Bill Curran 5 years ago updated by Tom 5 years ago 2
I can access Ubooquity via it's IP address on the web, but I've had no luck accessing it by it's FQDN (fully qualified domain name). Is this on purpose? I'm on a dynamic IP at home and want to access it during slow times at my business or remotely on my phone no matter where I am. If I can access ONLY by IP, I'll have to check it constantly. But via a DynDNS account I should be able to access it easily via FQND no matter how often the IP changes.Am I doing something wrong? Is this by design? Is this a feature request I'm now making?
Under review
There is nothing in Ubooquity's design that prevents the use of FQDN.
I created a no-ip.com account to test it today, and it worked (I pointed something like myname.ddns.net to my IP address and accessed it using myname.ddns.net:2202).

I don't know why it is not working on your side.