Wait, are you a schubadiver as well?

Something is completely shutting your server off from the internet, despite it having full LAN access. The only time I've run into this exact issue was when I misconfigured the firewall on a server, effectively only allowing for local connections. I simply started over by reinstalling Debian, wiping all my mistakes. But it could also be a setting on your router, and without you knowing what changes you made it's hard to give any reasonable advice.

These are just shots in the dark, and other might offer better solutions but I'd try;

1. Boot the laptop into a live session directly from USB. All settings are default. Test again, either wget or maybe ping a website. If it works, it's the server setup and I'd start over. If not...

2. Try reversing all changes on the router, give the server a different static IP.

3. Back up the router configuration to a file, consider making notes of important changes, reset the router and try again. If it STILL doesn't work you can restore the important settings. If it works, you can reimplement the settings from your notes. (unless we're talking manually imported VPN certificates and similar lol)

Sorry I wasn't able to help you out, I'm hosting from home and it's a fantastic thing when things

I don’t know if it’s useful or not, but if I boot a live debian USB in the server internet works

Haha yes, as mentioned. The issue is a setting on your laptop server installation. The simplest thing is just reinstalling and starting over.

Here I've tried wget https://104.18.114.97. It's able to connect to the IP on port 443, but shows an error message since I'm not using a domain name. But at least I know I've reached the server.

Please try wget https://104.18.114.97, if this one goes through I'd think the problem could be related to a faulty forwarding of regular internet traffic (port 80). If that fails as well I'd guess it's to due with the DHCP/Static IP's and involves your router. I'm absolutely clueless about Vodafone routers though.

Edit: Any connection would show "The certificate's owner does not match hostname ‘104.18.114.97’"

Yeah, I realized after the fact. This should work: wget 104.18.114.97, and you should get a ERROR 403: Forbidden if your server has any internet connection.

I bet it has something to do with the LAN DHCP setup, since you have to set a static IP for the server...

Update - That won't work at all if it is indeed the issue. Let me think for a sec on how to pull external ip by doing a IP wget...

I understand you might be a bit stressed out, but it's very hard to make head or tails of what you're describing.

E.g. What do you mean by "no internet connection"? Does it mean just the old laptop, all devices on the network or the router itself?

Everybody knows Facebook surveils, but seeing actual numbers is still newsworthy. Particularly when they're catastrophically high.

Money

Status

Being a moderator on an online forum

Domains can be free and several of them works flawlessly with DDNS for home hosting. You can set up a completely free Nextcloud. Self-signed certs and direct IP access works as well.

Somebody else mentioned setting up a VPN to your home LAN, that works fine too.

I like Bluetooth quite a lot, but the default SBC codec that comes with A2DP isn't all that great. Even FLAK gets recompressed in an obscure format at medium bitrate.

HD "standards" like... AptX(?) aren't really a Bluetooth standard AFAIK but it runs over Bluetooth so if both devices support it, it works great.

Fun fact, them HD standards are so software based that I got support for three different HD standards when I changed OS.

Due to the overall length it doubles as a guitar slide.

Also he likes to collect them. So, much more.