this post was submitted on 10 Dec 2025
9 points (100.0% liked)

Selfhosted

53946 readers
354 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.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

Hi, I have a problem accessing Paperless-ngx when I'm connected to my home network from a VPN. I've tried to make a simple sketch of my setup: Phone --> Wireguard --> Public Internet --> Unifi Wireguard server --> Home Network

Paperless-ngx is hosted on my server at 192.168.1.10:8000 But I can easily access all other services hosted on my server (192.168.1.10), e.g. homer (:8888) and Immich (:8080). It is just Paperless-ngx which doesn't work.

When at home and connected to my home WiFi I can also access Paperless-ngx.

Anyone having ideas to figure out, what is wrong in my setup? Or how to debug?

top 9 comments
sorted by: hot top controversial new old
[–] spaghettiwestern@sh.itjust.works 6 points 2 weeks ago (1 children)

Your WG network is a separate subnet. Add it to PAPERLESS_ALLOWED_HOSTS to allow access.

[–] StreetKid@reddthat.com 2 points 2 weeks ago

Without having time to test it yet, I think this is the issue.

[–] Brkdncr@lemmy.world 5 points 2 weeks ago (1 children)

Ping,Tracert,Knock on the port with Telnet.

I’m guessing firewall rules related to your vpn.

[–] StreetKid@reddthat.com 1 points 2 weeks ago (1 children)

Ping and traceroute are both successful. The IP is not the issue (I think), as all other services on the same server are working fine According to unifi firewall logs, nothing gets blocked when I attempt to access Paperless-ngx.

[–] Brkdncr@lemmy.world 1 points 2 weeks ago

Can you hit the port?

[–] oxfordcoma@lemmy.world 2 points 2 weeks ago* (last edited 2 weeks ago)

I’m not familiar with paperless but do you have PAPERLESS_BIND_ADDR set? maybe try to set it to 0.0.0.0

[–] StreetKid@reddthat.com 1 points 2 weeks ago

It must be a Paperless-ngx specific issue. Stopped Homer service available on :8888 and changed Paperless-ngx to be served on :8888 and it still doesn't work. This rules out firewall and network issues as Homer was accessible on this port.

[–] frongt@lemmy.zip 1 points 2 weeks ago (1 children)
[–] StreetKid@reddthat.com 1 points 2 weeks ago

Nothing in Unifi firewall logs nor Paperless-ngx logs. I'm using standard zones based a firewall rules in Unifi. And I looked through the firewall rules, and I don't find anything related to port 8000.