So i set up a rpi with home hassio at a remote location.
Did set up port forwarding and duckdns etc and it did work well for a couple of weeks.
Unfortunately i lost access to it.
I have set up the hassio to turn on/off some floodlights connected with unflashed sonoffs.
The internet is working well there, ( i can monitor my energy consumption through another platform).
At first i thought my sd card crashed but I know the hassio is operational as i can check that the lights are on (through the ewelink app) and that the duckdns ip address is being updated.
Is there something im missing? or some workaround?
I did yes, but as @nickrout said, the ssh port is not forwarded.
On second thought:
I could call the phone company and ask them to remotely access my router and forward the port.
What exactly should i ask for? and what would be the next steps?
Ask them to forward port, say, 222 external to port 22 on the fixed internal IP address you have set up.
I say to set the external port to something other than 22 because you’ll get bandits thumping on your door if you open 22. Security through obscurity is not really a thing, but it cuts down on traffic.
Then as soon as you can login install fail2ban. This will can login from a host if it has tried unsuccessfully, say, 3 times. Of course you can lock yourself out too if you have difficulty recalling your password.
If course that is not all there is to security, I am no expert.
You might like to consider nabu casa. Worth perhaps the $5 per month if this location is too far to make a quick drive to.
Turns out that the DuckDNS add-on stopped working.
I called the phone company, they gave me the current IP and i accessed it perfectly.
I also set up email notifications to notify me the external ip whenever it changes so i can always have this alternative.
The weird thing is though, that DuckDNS (although restarted) it wont update my current IP back to the site.
duckdns add-on logs:
# INFO: Using main config file /data/workdir/config
+ Account already registered!
Thu May 9 13:47:35 EEST 2019: OK
xxx.xxx.xxx.xxx (correct external IP)
UPDATED
# INFO: Using main config file /data/workdir/config
Processing XXXXXXX.duckdns.org
+ Checking domain name(s) of existing cert... unchanged.
+ Checking expire date of existing cert...
+ Valid till Jul 10 10:59:03 2019 GMT Certificate will not expire
(Longer than 30 days). Skipping renew!
Thu May 9 13:52:41 EEST 2019: OK
xxx.xxx.xxx.xxx (correct external IP)
NOCHANGE
Thu May 9 13:57:43 EEST 2019: OK
xxx.xxx.xxx.xxx (correct external IP)
NOCHANGE
...