Remote URL does not access

Hi Makers,
I am using Pi3 b+ with Mozilla IoT. I get issue on my remote URL https://aooddy.mozilla-iot.org I can’t access it but my internal URL https://gateway.local works so well. The error on browser shows as
Secure Connection Failed
An error occurred during a connection to aooddy.mozilla-iot.org. PR_CONNECT_RESET_ERROR

  • The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.

  • Please contact the website owners to inform them of this problem.

Please help me to fix it after I try to research many posted but it still unsuccessful.

Thanks you for supporting
Aooddy

That error generally occurs when your gateway is unable to connect the tunnel to our cloud service. You need to make sure that your gateway can reach the internet (e.g. ping google.com), and that it can reach our server at https://api.mozilla-iot.org:8443, e.g. curl -o /dev/null -s -w '%{http_code}' https://api.mozilla-iot.org:8443/ should yield a 404.

Also, one more question. When you first set up your gateway, did you let it finish completely, to the point that it automatically redirected you to your new domain?

The next thing to check is for PageKite related lines in the log file, e.g. grep -i pagekite ~/.mozilla-iot/log/run-app.log.

Thanks you for rapid replied mrstegeman :slight_smile: I had access my gateway via SSH then follow your list, so the result is

I can ping www.google.com successfully (67-200 ms) and get 404 after run the command which you recommend. finally I read run-app.log is showed e.g. 2020-05-22 00:54:08.165 INFO : PageKite connected!

Unfortunately, when I go step by step to install gateway. I got error after I setup my remote URL [ http://aooddy.mozilla-iot.org ]. The system redirect to my URL and showed error. So that I have to skip this process to register account and go step by step completely.

I am not sure the problem may occur from my internet router or not. I am using 4G Mobile Internet Router. My home area cannot get the fiber internet service. For my mobile router is D-Link DWR-953

Please advise me again how to fix the problem.
Great day…

It’s possible that PageKite is failing to keep the tunnel up over that connection.

If you are more of an advanced user, you could set up your own domain name with dynamic DNS and port forwarding, but that would be specific to your setup.

You are right “PageKite is failing to keep the tunnel up over that connection”. I found from internal log file in gateway. Anyway some parts in log shown as

2020-05-23 06:15:24.340 INFO : thing-url-adapter: Starting mDNS discovery
2020-05-23 06:15:24.456 INFO : thing-url-adapter: OUCH! - could not add membership to interface 192.168.1.55 { Error: addMembership EADDRINUSE
2020-05-23 06:15:24.459 INFO : thing-url-adapter: at Socket.addMembership (dgram.js:581:11)
2020-05-23 06:15:24.462 INFO : thing-url-adapter: at /home/pi/.mozilla-iot/addons/thing-url-adapter/node_modules/dnssd/lib/NetworkInterface.js:249:18
2020-05-23 06:15:24.466 INFO : thing-url-adapter: at Array.forEach ()
2020-05-23 06:15:24.469 INFO : thing-url-adapter: at Socket. (/home/pi/.mozilla-iot/addons/thing-url-adapter/node_modules/dnssd/lib/NetworkInterface.js:247:57)
2020-05-23 06:15:24.473 INFO : thing-url-adapter: at Socket.emit (events.js:198:13)
2020-05-23 06:15:24.476 INFO : thing-url-adapter: at startListening (dgram.js:128:10)
2020-05-23 06:15:24.480 INFO : thing-url-adapter: at state.handle.lookup (dgram.js:249:7)
2020-05-23 06:15:24.483 INFO : thing-url-adapter: at process._tickCallback (internal/process/next_tick.js:63:19)
2020-05-23 06:15:24.487 INFO : thing-url-adapter: errno: ‘EADDRINUSE’,
2020-05-23 06:15:24.491 INFO : thing-url-adapter: code: ‘EADDRINUSE’,
2020-05-23 06:15:24.494 INFO : thing-url-adapter: syscall: ‘addMembership’ }
2020-05-23 06:15:24.537 INFO : Finished updating add-ons

2020-05-23 06:16:04.337 INFO : Tunnel domain found. Tunnel name is: aooddy and tunnel domain is: mozilla-iot.org
2020-05-23 06:16:04.344 INFO : Tunnel name is set to: https://aooddy.mozilla-iot.org
2020-05-23 06:16:04.347 INFO : Local mDNS Service Domain Name is: gateway
2020-05-23 06:16:44.995 INFO : Tunnel domain found. Tunnel name is: aooddy and tunnel domain is: mozilla-iot.org
2020-05-23 06:16:45.003 INFO : Tunnel name is set to: https://aooddy.mozilla-iot.org
2020-05-23 06:16:45.006 INFO : Local mDNS Service Domain Name is: gateway
2020-05-23 06:59:30.643 INFO : Tunnel domain found. Tunnel name is: aooddy and tunnel domain is: mozilla-iot.org
2020-05-23 06:59:30.650 INFO : Tunnel name is set to: https://aooddy.mozilla-iot.org
2020-05-23 06:59:30.653 INFO : Local mDNS Service Domain Name is: gateway

It may used for fixing the problem or not?
Cheers

Those errors are from the Web Thing adapter, which is irrelevant to the current problem.

I will discuss with security policy team of mobile operator. The problem may be blocked by Sim card, then I will update again.

[Solved] I found my problem after I sit and solved it with team of mobile security. They reconfigured IP routing in network for me then explain that the Mozilla IoT Gateway standard configuration can operate with wire-line internet only, but for mobile internet has to protected.
If I want to get the service, mobile operator has to setup new policy for special case.