Working 600 km from home on my first big web project, with a raspberry pi as server (located at home). Decided to reboot it today in order to see if it would resolve a problem.

It probably booted up with a different local ip, cant access it anymore with ssh or ftp.

Fuck.

Rookie misstake: using dhcp

Dyndns? :D

@Linux you mean ddns. I am unable to see how dhcp would help?

Ddns with port forwarding should solve it. Unless ofcourse your ISP has hid your network behind his own private network.
Which I am assuming it is not because you are able to access it now.
Hence ddns is the way.
(Noip.com dyndns.com etc)

@rohitshetty he has dhcp on his local network. Cant see how this rant could make sense otherwhise

@rohitshetty he wrote that his Pi was at home.

I cant see how DynDNS would help here..

@Linux ah. I thought you meant using dhcp. Will fix this.
Reading comments when sleepy does this I guess.
Yes using dhcp has caused this. Static config would have been great.
And I said ddns because I thought the ip address of home network changed
Yes you are write. Just stopping using dhcp will solve the issue :) my bad.

@rohitshetty
Static IP 😍

Well, dynamic DNS is a beauty too. Personally I am in love with afraid.org DNS service, can really recommend it!

Static DHCP... Work smarder not harder.

Well that's why I have two raspberry pis with wiring to boot one from another. And yes I run dhcp on both pis and they both have static IP.

@digli Get a VPS while you resolve the issue or at least until you get back home.

If anything goes wrong and you can't use a VPN try Weaved (now I think they use the new name remot3.it)

Why does one set the lease time so ridiculously low? 🤔