Issues with Cloudron Login Integration for Open WebUI
-
Hello Cloudron Developers,
I'm encountering persistent issues when trying to use the Cloudron Login with the Open WebUI app. Here's a summary of what I'm experiencing:
When first setup 2 months ago we had no issues with login.
Problem Summary:
- Already logged in users stay logged in, no issues accessing.
- When I attempt to access Open WebUI as a new user, the usual Cloudron SSO (Single Sign-On) login page appears. Login via cloudron sends to domain.org.uk:/3000 causing a 404 error.
- If the user has already logged in in the past, the login page just refreshes after clicking Login with Cloudron.
Issue 2
- We found that the Setup Page was showing the UI URL with .org.uk:/3000. Not changed by us.
- We changed it to org.uk:3000, and now the error page after login shows Site can not be reached, and it took too long to respond.
- I am unable to enter or use the application as expected via Cloudron user accounts.
Setup Details:
- Cloudron Version: 8.3.2
- Open WebUI app version: OpenWebUI 0.9.2
- Browser(s) tested: Chrome
- Setup as Cloudron Login not Dedicated Accounts
Troubleshooting Steps So Far:
- Tried private/incognito mode (to rule out cookies/cache).
- Rebooted both the app and the server.
- Installed a fresh copy of Open WebUI from the Cloudron app store to recreate.
- Checked app logs (found no specific error related to login failures).
- Confirmed that LDAP is not enabled on the settings page and was set as disabled by default for the new install of Open WebUI, even though I selected the login with cloudron option.
- No issues reported with Cloudron user accounts elsewhere.
Questions/Further Information Needed:
- Is this a known issue with the current Open WebUI package or with Cloudron’s SSO?
- Are there any configuration files or settings inside Open WebUI that need manual adjustment for Cloudron SSO?
- Any guidance on specific logs to check, or debug flags to enable for more insight?
- If others have had success with this combination, could you outline the steps or version details?
Thanks in advance for any advice or suggestions. Happy to provide logs or further information if needed. Looking forward to a solution so I can integrate Open WebUI smoothly into our Cloudron workflow.
-
To solve this issue please take a look here as the solution. It might not be the best solution that you expect, but so far, this can resolve your issue
-
Thanks, but if we revert to an old backup, then we will lose information and models made.
I think we will look at something else. Cloudron seems to be lacking when it comes to AI apps. Easypanel has about 7
Thank you for the help.
@apesorguk you don't need to revert to old backup, with the latest update just enter the information of your openwebui instance. You enter with www.yourdomain.com:3000 as admin then go to setting > General and then enter your domain
-
@apesorguk
When you are using the latest version, on every app restart the correct domain is set.
Please update to the latest version and restart app.
Please report back if this solves the issue.Cloudron say no updates available, so assume it is all up to date.
Open WebUI OpenWebUI 0.9.2 (Ollama 0.9.2)
Version
v0.6.15
(latest)The correct domain is set every restart
but when URL is set to sub.domain.org.uk:3000 just hangs the next page saying there is no response
and when set to sub.domain.org.uk the login page just keeps refreshing when clicking Login with cloudron.
is it meant to be sub.domain.org.uk or sub.domain.org.uk:3000 also do you put https:// or not.
-
Yep, that worked. So, tell me?
- If the field is meant to be blank. Why are fresh installs completing the field with the URL set at install via Cloudron?
- Also, if that being that it is automatically being filled at the time of install, why is it allowing cloudron logins?
-
Yep, that worked. So, tell me?
- If the field is meant to be blank. Why are fresh installs completing the field with the URL set at install via Cloudron?
- Also, if that being that it is automatically being filled at the time of install, why is it allowing cloudron logins?
@apesorguk said in Issues with Cloudron Login Integration for Open WebUI:
If the field is meant to be blank.
I've never stated it is meant to be blank.
I have stated on each restart we configure this. The OpenWebUI does not always refelect the settings in the database in the UI.@apesorguk said in Issues with Cloudron Login Integration for Open WebUI:
Also, if that being that it is automatically being filled at the time of install, why is it allowing cloudron logins?
Sorry, I don't understand what you mean with this question.
We set the.webui.urlin the startup directly into the database.
See https://git.cloudron.io/packages/openwebui-app/-/blob/main/start.sh?ref_type=heads#L71-L78 -
@james said in Issues with Cloudron Login Integration for Open WebUI:
@apesorguk said in Issues with Cloudron Login Integration for Open WebUI:
If the field is meant to be blank.
I've never stated it is meant to be blank.
I have stated on each restart we configure this. The OpenWebUI does not always refelect the settings in the database in the UI.(So basically it's buggy and is duplicating entries by entering it into the database at install, and conflicting if editing or changing the .WEBUI.URL within the UI after install? If this is the case, why not lock the field like in IMMICH app, where it says settings are controlled by a file and locks admin settings from being changed? Bearing in mind that in the UI it says https://localhost:3000 in the field when empty, making it seem like that is the type of format that needs to be in the field? (seen by a novice)
@apesorguk said in Issues with Cloudron Login Integration for Open WebUI:
Also, if that being that it is automatically being filled at the time of install, why is it allowing cloudron logins?
Sorry, I don't understand what you mean with this question.
We set the.webui.urlin the startup directly into the database.
See https://git.cloudron.io/packages/openwebui-app/-/blob/main/start.sh?ref_type=heads#L71-L78When you install a fresh install of Open WebUI it automatically fills .WEBUI.URL with what is entered here in the screenshot. Bearing in mind, I selected to allow all users from the cloudron option.
Now if having .WEBUI.URL filled with the URL of your install stops Cloudron login from working. Why is it being auto-filled with the Open WebUI URL when selecting Allow all users from the cloudron?
@james said in Issues with Cloudron Login Integration for Open WebUI:
You have to put nothing in there. (I did not put that there; you insinuated I had. The URL there was the URL installed by Cloudron at the time of install.)
Leave the field alone. Don't type anything in there by hand. (I did not change or type anything in manually. This error with cloudron login started maybe a week or two ago. 2-3 months after initial setup.)
Restart the app, this should solve the issue. (Thanks, removing and leaving blank worked, users can now login again with login with cloudron)Since removing the URL set in .WEBUI.IRL in the UI, my users can now log in to Open WebUI with cloudron login.
-
@james said in Issues with Cloudron Login Integration for Open WebUI:
@apesorguk said in Issues with Cloudron Login Integration for Open WebUI:
If the field is meant to be blank.
I've never stated it is meant to be blank.
I have stated on each restart we configure this. The OpenWebUI does not always refelect the settings in the database in the UI.(So basically it's buggy and is duplicating entries by entering it into the database at install, and conflicting if editing or changing the .WEBUI.URL within the UI after install? If this is the case, why not lock the field like in IMMICH app, where it says settings are controlled by a file and locks admin settings from being changed? Bearing in mind that in the UI it says https://localhost:3000 in the field when empty, making it seem like that is the type of format that needs to be in the field? (seen by a novice)
@apesorguk said in Issues with Cloudron Login Integration for Open WebUI:
Also, if that being that it is automatically being filled at the time of install, why is it allowing cloudron logins?
Sorry, I don't understand what you mean with this question.
We set the.webui.urlin the startup directly into the database.
See https://git.cloudron.io/packages/openwebui-app/-/blob/main/start.sh?ref_type=heads#L71-L78When you install a fresh install of Open WebUI it automatically fills .WEBUI.URL with what is entered here in the screenshot. Bearing in mind, I selected to allow all users from the cloudron option.
Now if having .WEBUI.URL filled with the URL of your install stops Cloudron login from working. Why is it being auto-filled with the Open WebUI URL when selecting Allow all users from the cloudron?
@james said in Issues with Cloudron Login Integration for Open WebUI:
You have to put nothing in there. (I did not put that there; you insinuated I had. The URL there was the URL installed by Cloudron at the time of install.)
Leave the field alone. Don't type anything in there by hand. (I did not change or type anything in manually. This error with cloudron login started maybe a week or two ago. 2-3 months after initial setup.)
Restart the app, this should solve the issue. (Thanks, removing and leaving blank worked, users can now login again with login with cloudron)Since removing the URL set in .WEBUI.IRL in the UI, my users can now log in to Open WebUI with cloudron login.
@apesorguk said in Issues with Cloudron Login Integration for Open WebUI:
Since removing the URL set in .WEBUI.IRL in the UI, my users can now log in to Open WebUI with cloudron login.
Great to read it is working now.
