You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When accessing the Fredy Web UI via a local IP address over HTTP, the login process fails silently on an existing setup. The page reloads and clears the input fields without logging the user in. However, accessing the exact same container via a reverse proxy (Nginx Proxy Manager) over HTTPS works perfectly. Tried another browser or incognito tab, doesnt matter.
A completely fresh test container also works over HTTP, indicating the issue only occurs on the existing instance.
Steps to Reproduce
Access the Fredy Web UI via a local IP and port over HTTP.
Enter valid login credentials into the provided fields, click Login
Observe that the page briefly reloads, and the input fields are cleared, but you remain logged out
Access same instance over NPM with domain and HTTPS
Repeat steps, login works
Expected Behavior
The login should succeed, granting access to the Web UI, or an explicit error message should be displayed in the UI indicating why the login failed.
Actual Behavior
The page reloads and the login fields are cleared. The user remains logged out. There are no obvious error messages in the UI, and the browser console/network tab (tested in Firefox) does not show any visible errors.
Screenshots / Logs
Debug Log stays at 0%, so here is a video instead. Doesnt matter if credentials are manually pasted or filled from the password manager.
No error in browser console or network tab too.
Bug Description
When accessing the Fredy Web UI via a local IP address over HTTP, the login process fails silently on an existing setup. The page reloads and clears the input fields without logging the user in. However, accessing the exact same container via a reverse proxy (Nginx Proxy Manager) over HTTPS works perfectly. Tried another browser or incognito tab, doesnt matter.
A completely fresh test container also works over HTTP, indicating the issue only occurs on the existing instance.
Steps to Reproduce
Expected Behavior
The login should succeed, granting access to the Web UI, or an explicit error message should be displayed in the UI indicating why the login failed.
Actual Behavior
The page reloads and the login fields are cleared. The user remains logged out. There are no obvious error messages in the UI, and the browser console/network tab (tested in Firefox) does not show any visible errors.
Screenshots / Logs
Debug Log stays at 0%, so here is a video instead. Doesnt matter if credentials are manually pasted or filled from the password manager.
No error in browser console or network tab too.
20260811-1416-59.3412783.mp4
Environment
App version: 25.2.1, Docker: yes
Additional Context
Docker Compose: