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.
  • Mir@programming.devOP
    link
    fedilink
    English
    arrow-up
    1
    ·
    6 months ago

    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
      link
      fedilink
      English
      arrow-up
      1
      ·
      6 months ago

      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.devOP
        link
        fedilink
        English
        arrow-up
        1
        ·
        6 months ago

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