Describe the bug
When running RomM for the first time, the onboarding page appears to be blocked behind authentication - despite the onboarding being required in order to have a valid authentication
To Reproduce
Set up RomM from scratch with or without a reverse proxy (I tried accessing the app through both methods), and navigate to the app in a web browser (probably relevant: I am not on 'localhost', my host is a VPS in Europe and I'm accessing the app from my home in the US).
The app will initially load the main interface (which, by the way, is also a problem) and hold there for a few seconds before navigating to '/login?next=/setup'. When manually trying to navigate to 'domain.com/setup', it just redirects back to this same page.
Expected behavior
If the app is set to go through the onboarding, it should go to the onboarding, not the regular login page.
Ideally, an LDAP integration would negate the issue entirely (for those of us who use it), but I know that's a much bigger problem than simply stopping a redirect.
Screenshots
Relevant sections of docker-compose file:
Well that was fast. I should have tried it first, but clearing cookies stopped the redirect loop. I have no idea what cookie or when it was created that caused the failure.
RomM version v3.5.1
Describe the bug When running RomM for the first time, the onboarding page appears to be blocked behind authentication - despite the onboarding being required in order to have a valid authentication
To Reproduce Set up RomM from scratch with or without a reverse proxy (I tried accessing the app through both methods), and navigate to the app in a web browser (probably relevant: I am not on 'localhost', my host is a VPS in Europe and I'm accessing the app from my home in the US).
The app will initially load the main interface (which, by the way, is also a problem) and hold there for a few seconds before navigating to '/login?next=/setup'. When manually trying to navigate to 'domain.com/setup', it just redirects back to this same page.
Expected behavior If the app is set to go through the onboarding, it should go to the onboarding, not the regular login page.
Ideally, an LDAP integration would negate the issue entirely (for those of us who use it), but I know that's a much bigger problem than simply stopping a redirect.
Screenshots Relevant sections of docker-compose file:
Screenshots of nginx-proxy-manager settings for RomM:
last bit of logs from 'docker logs romm'