Selfhosted

40201 readers

889 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:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

[solved] Can’t login to Syncthing GUI with Ngnix Proxy Manager (programming.dev)

submitted 6 months ago* (last edited 6 months ago) by Mir@programming.dev to c/selfhosted@lemmy.world

15 comments fedilink hide all child comments

Edit: Solution is in Nginx I disabled these: Cache Assets, Block Common Exploits, Websockets Support.

I can login using the local IP 192.168.1.2:9101, but when I route that with Nginx, It won't.

I have the GUI listen address as : 0.0.0.0:9101

I've been googling for hours but I can't find anything, In browser console it says

Failed to load resource: the server responded with a status of 403 ()

syncthing.my.domain.com/:1  Refused to execute script from 'https://syncthing.my.domain.com/meta.js' because its MIME type ('text/plain') is not executable, and strict MIME type checking is enabled.

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

[–] pyrosis@lemmy.world 1 points 6 months ago* (last edited 6 months ago) (1 children)

My npm has web sockets enabled and blocking common exploits.

Just checked syncthing and it's set to 0.0.0.0:8384 internally but that shouldn't matter if you changed the port.

When Syncthing is set to listen on 0.0.0.0, it means it's listening on all available network interfaces on the device. This allows it to accept connections from any IP address on the network, rather than just the local interface. Essentially, it makes Syncthing accessible from any device within the network.

Just make sure you open those firewall ports on the server syncthing is running on.

Btw the syncthing protocol utilizes port 22000 tcp and udp. Udp utilizing a type of quic if you let it.

So it's a good idea to allow udp and tcp on 22000 if you have a firewall configured on the syncthing server.

Edit

Wording for firewall ports and the purpose of 0.0.0.0

[–] Mir@programming.dev 1 points 6 months ago

I have it set to 0.0.0.0, and I can access it from another pc using the ip:port address. But when I try to access using the domain name it shows the login page but I can't login, it just refresh the page and I can see the error above in the logs.