this post was submitted on 18 Jun 2023
14 points (93.8% liked)

Selfhosted

39180 readers
511 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

Hi all,

Apologies if this isn't the correct place to ask, if not just point me in the right direction.

Hopefully someone can help me with this as i've been struggling for a while now. Previously i've been using the free Oracle VPS to proxy some services that are being ran from my local server to access them without tailscale but am now looking to host some stuff myself on it like FreshRSS.

I'm running Ubuntu 22.04.2 LTS (GNU/Linux 5.15.0-1037-oracle aarch64) on the VPS, Nginx Proxy Manager and using Cloudflare for domain stuff.

The issue is, whenever i try to access the URL of something set up on the VPS with the IP on NPM set to either the private IP, localhost, VPS tailscale IP or 127.0.0.1, i get a 502 error from cloudflare, however, if i set that same proxy host to the tailscale IP and port of something on my local server, it works fine, which suggests to me it's something LAN related on the VPS i need to sort but i just can't figure out what.

Anyone got any ideas?

EDIT: Turns out it was due to iptables on the VM. https://lemmy.world/comment/325214

you are viewing a single comment's thread
view the rest of the comments
[–] Garthski 1 points 1 year ago

That was it thank you! I seen that ufw was inactive and assumed there wasn't anything else on the VM but i dug deeper and seen i needed to allow it in iptables.