Selfhosted

40347 readers

334 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 7 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

[–] lemmyvore@feddit.nl 3 points 6 months ago (3 children)

I'm a bit confused about those ports (9000 and 9101) because afaik Syncthing only listens on 8384 (GUI) and 22000 (transfers).

I'm using it with NPM as well and I haven't needed to do anything special to access the GUI through NPM beyond pointing NPM at the syncthing address and port (which, again, I used 8384).

Please note that 22000 is unrelated to the GUI, that needs to be handled as a stream. It's not HTTP so you won't be able to do domain routing with it. You can add it as a stream host in NPM but it will use the IP/name of the machine/container that NPM runs on.

I currently expose 22000 to Tailscale through the tailnet IP/name. But you only need to define that in the other syncthing clients anyway, shouldn't impact using the GUI.

[–] Mir@programming.dev 1 points 6 months ago (2 children)

Sorry it's just 9101, I updated it.

In GUI you can change the port of the GUI and that's what I did, so I can right now actually access it using 192.168.1.2:9101 and it works. Do you have NPM configured in anyway other than pointing? have you made any changes in Syncthing itself to give it a domain name or an address?

[–] lemmyvore@feddit.nl 1 points 6 months ago (1 children)

No relevant changes in Syncthing. The GUI is on 0.0.0.0:8384, transfer is on tcp4://0.0.0.0:22000.

NPM is a simple forward to IP:8384. I have unchecked cache, block exploits and websockets in NPM.

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

The forwarding is actually taking place, the problem is that when I write credintials and try to login it doesn't