Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Firefly III
  3. Issue with LDAP/OIDC when 1st installing behing reverse proxy

Issue with LDAP/OIDC when 1st installing behing reverse proxy

Scheduled Pinned Locked Moved Firefly III
3 Posts 2 Posters 152 Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • N Offline
    N Offline
    Neiluj
    wrote on last edited by
    #1

    Hi,

    A quick disclaimer to the below: using Cloudron behind a reverse proxy is not officially supported.

    With this being said at the moment and with Cloudron being behind NPM in a lab environment:

    • When first installing, leaving user management to the app, everything work fine and the first time a user access Firefly III, the user is prompted to create an admin Firefly III user
    • However, when first installing and choosing for user access to be cloudron managed (OIDC) then, upon first login, the user get the possibility to "Login with Cloudron", but clicking on the login button result in an openresty 502 Bad gateway Error (presumably from NPM).

    Additional info:

    • There is no relevant info in the Cloudron server logs
    • The favicon is fetched correctly in both scenario (shows up on the 502 error page)

    I am still filtering through the NPM logs but since this instance is serving everything and anything, it is taking a while to "comb".

    What is throwing me off a bit is the reason behind it working with no Cloudron user access management and, not working when Cloudron manage user access.

    I presume that this could have to do with the Remote User Guard settings / Headers

    Maybe someone already ran into this situation or we have some NPM experts around here?
    Any tips?

    Many thanks,

    1 Reply Last reply
    0
    • J Online
      J Online
      joseph
      Staff
      wrote on last edited by
      #2

      Is NPM already added as a trusted proxy - https://docs.cloudron.io/networking/#trusted-ips ? Other than that, I don't know much about NPM to help..

      1 Reply Last reply
      0
      • N Offline
        N Offline
        Neiluj
        wrote on last edited by
        #3

        @joseph Thanks for the suggestion. I have added the NPM IP as a trused IP and so far, no success, the 502 error is still there.

        1 Reply Last reply
        0
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Bookmarks
        • Search