Selfhosted

39435 readers

4 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

[SOLVED, user error] Proxmox not conncected to internet, but is reachable on LAN (sopuli.xyz)

submitted 7 months ago* (last edited 7 months ago) by [email protected] to c/[email protected]

46 comments fedilink hide all child comments

[SOLVED] Turns out I'm just a bigger moron than I thought. The MAC address of my server had accidentally been flagged in my router for black listing.

As the title says, my proxmox host is apparently not able to reach the internet anymore, not sure for how long this has been an issue, I rarely work on the host itself. It can ping other devices on my network just fine, and other devices can ping it. I can also SSH in to it and access the web interface. My VMs are connected to the internet without any issues. I don't need to access the host remotely/outside my home network, this is just for updating it etc.

I can't see the host under active devices in my router though.

I have been trying to figure why, but so far without any luck.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 0 points 7 months ago (1 children)

Try a traceroute to something like 9.9.9.9 and google's IP. You're able to resolve things ok. So, not DNS. Need to find out where the traffic is going to die.

Also, try a curl https://google.com -vvv. This should give some more info on what is happening to TCP traffic.

[–] [email protected] 0 points 7 months ago

this is the output when i run curl httpS://google.com -vvv