Gateway not accessible after restart


My gateway is not accessible remotely using subdomain after i restart my internet modem and gateway. I can access it first time after setting up fresh.

Sorry to hear you’re having troubles. Are you able to access http://gateway.local on your local network?

If not, you’ll need to either enable SSH on your Raspberry Pi or hook up a monitor and keyboard to debug a few things.

Yes i am able to access it via gateway.local and also able to ssh to pi@gateway.local. Here is the log

2019-11-05 04:11:13.392 INFO   : Checking for add-on updates...
2019-11-05 04:11:14.952 INFO   : Finished updating add-ons
2019-11-05 04:11:46.325 INFO   : Tunnel domain found. Tunnel name is: muglani and tunnel domain is:
2019-11-05 04:11:46.329 INFO   : Tunnel name is set to:
2019-11-05 04:11:46.331 INFO   : Local mDNS Service Domain Name is: gateway
2019-11-05 04:11:46.860 ERROR  : Failed to get property level: getProperty: device: http---led-lamp.local-things-lamp not found.
2019-11-05 04:11:46.862 ERROR  : Failed to get property on: getProperty: device: http---led-lamp.local-things-lamp not found.
2019-11-05 04:21:46.538 INFO   : Opening database: /home/pi/.mozilla-iot/log/logs.sqlite3
2019-11-05 04:21:47.971 INFO   : wifi-setup: waitForWiFi: networks exist: [ 'Gamers Heaven Ultra' ]
2019-11-05 04:21:48.112 INFO   : wifi-setup: waitForWifi: connection found
2019-11-05 04:21:48.118 INFO   : DNS config is: gateway
2019-11-05 04:21:48.120 INFO   : Service Discovery: changing profile - local domain is now: gateway
2019-11-05 04:21:50.161 INFO   : Service Discovery: state changed to: true
2019-11-05 04:21:50.180 INFO   : HTTP server listening on port 8080
2019-11-05 04:21:50.274 INFO   : Loading add-on: thing-url-adapter
2019-11-05 04:21:50.965 INFO   : thing-url: Opening database: /home/pi/.mozilla-iot/config/db.sqlite3
2019-11-05 04:21:51.006 INFO   : thing-url: Loading add-on for thing-url-adapter from /home/pi/.mozilla-iot/addons/thing-url-adapter
2019-11-05 04:21:51.508 INFO   : thing-url: Starting mDNS discovery
2019-11-05 04:22:00.322 INFO   : Checking for add-on updates...
2019-11-05 04:22:01.951 INFO   : Finished updating add-ons

Ok, next question. Are you able to access the internet from the gateway? For example, can you ping

yes i can ping google.

Hmm, ok.

  1. Can you ping
  2. Does the following print out “200”?
    curl -s -o /dev/null -w '%{http_code}'
  3. Does the following output 2 separate processes?
    ps -ef | grep '[p]agekite\.py'
  4. Are there any log lines with “pagekite”?

I cannot ping

even from my pc. Attached output of your test.
If i run this

ps -ef | grep

then there is a line but not with your command.

The ping won’t work, as we don’t pass pings through the firewall. I meant to remove that from my previous response.

So, from your screenshot, I can see that you are able to reach the registration server. However, since pagekite isn’t running, your tunnel will not be active.

From your log, it looks like may not actually have the subdomain set up. Can you try this?

sqlite3 ~/.mozilla-iot/config/db.sqlite3 "select value from settings where key = 'tunneltoken' or key = 'notunnel'"

If you get output containing {"name":"something","token":"something else"}, please omit/change the “something else” before posting here.

Also, could you send a complete log to me?

It is fixed today. I think i know what is the issue. I will verify and post it here.

I think the reason behind the issue was that i did not let the domain set process complete when i was setting up gateway. It was processing and taking too much time so i clicked skipped. Domain was still set and i was able to access it but after restart it did not work. I checked that tunnel token was set but notunnel was true. I followed this thread

Remote tunnel access denied

and reclaimed domain and also set notunnel=false manually. It works since then. I read somewhere that while setting up domain if at continues processing and takes too much time we can skip and still domain will be set but looks like this creates the issue i got.

Glad you got it working.

I’m actually trying to work through some of these setup issues as we speak.