Page 1 of 2
DDNS not working
Posted: Sun Oct 18, 2020 4:06 pm
by alexT
Hello, I've added my no-ip.com account into my Gargoyle
router's DDNS setup. When I force update, Gargoyle responds: Update successful.
However, when I go to the domain no-ip gave me, I get page not found error.
I have no problem logging into Gargoyle remotely using https using my ip and :443. Problem is just with my no-ip domain.
I wonder if this could be due to the fact that port 443 also should be declared? But putting :443 in front of the no-ip domain also doesn't work. Says "this page not working"
Re: DDNS not working
Posted: Sun Oct 18, 2020 5:00 pm
by Lantis
You're definitely visiting the HTTPS variant of your domain (rather than specifying :443)?
Can you confirm either in the Gargoyle logs or noip site that the correct IP is being updated?
Re: DDNS not working
Posted: Mon Oct 19, 2020 9:52 am
by alexT
Hi Lantis,
Logread shows updates (when needed) are successful. Most of the time log says it checked and update not necessary.
You're definitely visiting the HTTPS variant of your domain (rather than specifying :443)?
No. I just realized that even though I put :443 in front of my ip when logging in on the web, in Chrome https is crossed out. It does that because I need some kind of security certificate?
Web Admin Protocol in Router Access tab is set to "http & https"
Re: DDNS not working
Posted: Mon Oct 19, 2020 3:53 pm
by RomanHK
in Chrome https is crossed out. It does that because I need some kind of security certificate?
Yes, you must have a validated certificate for the https protocol to work properly. I recommend using the OpenWrt package "ACME" (Let's Encrypt), which is free.
... of course, you need to have space in the router for additional libraries.
Re: DDNS not working
Posted: Mon Oct 19, 2020 5:26 pm
by Lantis
Doesn't matter if it is crossed out. As long as it is there. I was just pointing out the difference between
http://example.com:443
And
https://example.com
Both go to port 443 on the destination server, but the first one attempts to establish an insecure connection and is often refused or errors. Specifying the port alone is not enough.
Of course when you use https, this also implies 443 implicitly.
Re: DDNS not working
Posted: Mon Oct 19, 2020 5:27 pm
by Lantis
So different question, forgetting noip for a moment.
If you navigate to
https://your-ip-address
Do you get the result you want or does that not work as well?
Re: DDNS not working
Posted: Thu Oct 22, 2020 2:33 am
by alexT
HI Lantis, Yes, I can connect to Gargoyle remotely over the web (
https://my-ip-address) and via SSH with no problem.
(Has to be from a different IP than my own. If I try over LAN, I get a Forbidden message).
But as I said, using the domain no-ip gave me, I get "ERR_CONNECTION_REFUSED" message in Chrome.
Re: DDNS not working
Posted: Sat Oct 24, 2020 6:08 am
by alexT
I realized that if logging in with ip doesn't work, I could just login into no-ip.com account and see what my new ip is and then connect to gargoyle using the new ip.
But it would be nice to be able to login with the domain no-ip gave me.
Does anyone have any trouble logging into gargoyle using a no-ip domain?
Re: DDNS not working
Posted: Sat Oct 24, 2020 6:43 am
by RomanHK
1) check the settings in the router according to the screenshot:
2) do not create any port forwarding 443 - gargoyle will perform the forwarding itself!
3) try
https://my-ip-adress from outside - if you do it from the LAN side, a so-called loopback can be done and it can work.
4) try other browsers.

If you do not get to the address
https://my-ip-adress from outside, you will be behind NAT and the connection will fail (you do not have a public IP address).

can you reach
https://my-ip-adress from outside?
Re: DDNS not working
Posted: Sat Oct 24, 2020 10:43 pm
by alexT
Hi RomanHK,
I feel very foolish.
Remote Web Admin Access says https but I was trying
http://domain instead of
https://domain.
What threw me off was that
Web Admin Protocol: says
http & https so I had assumed http should also work.
Thank you all for your help and sorry for being so daft.