Cloudron Forum

@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.url in the startup directly into the database.
See https://git.cloudron.io/packages/openwebui-app/-/blob/main/start.sh?ref_type=heads#L71-L78

When 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.

Yep, that worked. So, tell me?

1. If the field is meant to be blank. Why are fresh installs completing the field with the URL set at install via Cloudron?
2. Also, if that being that it is automatically being filled at the time of install, why is it allowing cloudron logins?

@james

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.

Yes, we did. Sorry, we tried posting in the App Wishlist category, but it was loading a white page yesterday, which prevented us from posting.

We played around further with it on https://lobechat.com/

No issues with advanced params, unlike Open WebUI, in lobe chat, you set it in a beautiful UI, and it even tells you when you try it if that model can not handle those params and tells you what model can.

@firmansi

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.

We would love to see

https://github.com/lobehub/lobe-chat

Experience AI reasoning like never before. Watch as complex problems unfold step by step through our innovative Chain of Thought (CoT) visualization. This breakthrough feature provides unprecedented transparency into AI's decision-making process, allowing you to observe how conclusions are reached in real-time.

By breaking down complex reasoning into clear, logical steps, you can better understand and validate the AI's problem-solving approach. Whether you're debugging, learning, or simply curious about AI reasoning, CoT visualization transforms abstract thinking into an engaging, interactive experience.

We have used it on Easypanel and it's a nice bit of kit.

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.

Although just to let you know, I found a quicker and easier way of fixing just by adding the Birthday Field to a category called Profile Information fixed it.

Slightly confused everywhere saying this is fixed but I still get this issue when installing the Birthday App.

Invalid database configuration
SQLSTATE[42S22]: Column not found: 1054 Unknown column 'profile.birthday' in 'field list' The SQL being executed was: SELECT *, `user`.*, `profile`.*, DATE_ADD(profile.birthday, INTERVAL YEAR(CURDATE())-YEAR(profile.birthday) + IF((CURDATE() > DATE_ADD(`profile`.birthday, INTERVAL (YEAR(CURDATE())-YEAR(profile.birthday)) YEAR)),1,0) YEAR) as next_birthday FROM `user` LEFT JOIN `profile` ON `user`.`id` = `profile`.`user_id` WHERE (DATE_ADD(profile.birthday, INTERVAL YEAR(CURDATE())-YEAR(profile.birthday) + IF((CURDATE() > DATE_ADD(`profile`.birthday, INTERVAL (YEAR(CURDATE())-YEAR(profile.birthday)) YEAR)),1,0) YEAR) BETWEEN CURDATE() AND DATE_ADD(CURDATE(), INTERVAL 2 DAY)) AND (`user`.`status`=1) ORDER BY `next_birthday` LIMIT 10

But yet this link https://git.cloudron.io/packages/humhub-app/-/commit/aec1ea94b82b8ba26ab6504aefecfe0198478a23 and this post says it's not an issue.

So I have played about for days, I did this because when trying EmClient, it said there was an SSL issue, and it was not the only place I saw an SSL error, and when clicking reissue, I saw there were lots of issues with trying to generate a SSL for imap.domain.name

I changed the mail server URL from imap.domain.name to my.domain.name and then checked DNS. I noticed the DNS had not been updated, did it manually. I checked the logs as the process was being done, it stated that the DNS record had been updated, but it had not.

Since changing my mail server address to the same URL as my cloudron server, the connection seems to be more stable, with faster responses and no SSL errors.

Outlook it still not working and seems to find the old URL where as all other apps are seeing the new URL and still loading the imap.domain.name, we have given up on this issue.

What is the point in being able to change the domain name and subdomain of the mail server when it don't seem to be liked by mail clients.

@BrutalBirdie

I tried again and yes i got a log

{
  "mailboxId": "*****@******",
  "userId": "uid-8b2c5664-0d65-47d7-98a2-89c9e4b48174",
  "user": {
    "id": "uid-8b2c5664-0d65-47d7-98a2-89c9e4b48174",
    "username": "******",
    "email": "*****@******",
    "fallbackEmail": "",
    "displayName": "My Name",
    "groupIds": [
      "gid-19ce00de-f2e3-4217-8a87-9012cc97586a",
      "gid-4672cf66-1559-4beb-9895-22d3d5807557",
      "gid-501f5f99-202f-4942-a8bd-bb2629a4e1cd",
      "gid-5d8ff4e5-370a-4604-bb28-bd3f68c8d6b6",
      "gid-62b2f265-e008-4ec8-a2f2-3f528525f7be",
      "gid-70d9d027-c3b2-403e-9635-283a8522d5c5",
      "gid-84f959b8-4746-47af-ad5a-2f0efc19345a",
      "gid-8df3f45d-d9fc-4771-af81-867e4fd2605a",
      "gid-8eae84c6-5e8b-4dfa-a562-2d7e16e718ab",
      "gid-99206b9e-df93-439d-a7aa-0ee73529af33",
      "gid-bc492655-bead-4c4e-b466-f5675ee46377",
      "gid-c7054bed-90b9-4e09-9499-b0e1f5daa2df",
      "gid-d99bd0a5-5508-4cc2-a9c2-9018d72b9b63",
      "gid-eaaef63b-db0f-4eb8-be63-91864e00352e",
      "gid-eed83b9d-d390-415b-a2f0-ef1b59373992",
      "gid-f2348d21-c47f-4f5d-b1a2-5e51fb1d68ae",
      "gid-f26108fb-5daf-4cf2-b333-babbf80e032c",
      "gid-fc49f169-73af-40f0-a168-7efdcb42078b"
    ],
    "active": true,
    "source": "",
    "role": "owner",
    "twoFactorAuthenticationEnabled": false,
    "notificationConfig": [
      "appUp",
      "appDown",
      "appOutOfMemory",
      "backupFailed",
      "certificateRenewalFailed"
    ],
    "inviteAccepted": false
  }
}

I have marked out personal details. Can not see and issue.

I found this

https://answers.microsoft.com/en-us/outlook_com/forum/all/invalidcredentials-temporarilyunavailable/767c013a-0b92-46ec-b188-589563ed27e2

it seems to be a common issue not just with cloudron servers, but other servers. I have had a look at the credentials sorted on my Microsoft account and there is none there as far as I can see in relation to my Mail server and Outlook.

@fbartels

We have used the same address for 1 year. Please be rest assured everything was working until we upgraded to Cludron 3.8.0

Before this, nothing has changed. We only came across this error because Outlook wanted to connect to the settings it had and could not, it has nothing to do with DNS Records or server setup.

Also DNS issues would affect all Webmail Clients not just singular Outlook.

I have tested Thunderbird. Spark Desktop, eM Client, Mailbird, the only one that can not connect is Outlook.

@fbartels

Also to verify we have done a manual setup of the connection

Confirming trying to connect to IMAP not cloud services
Before upgrading to 8.3.0 at this point it connected fine.

And same result of

and the same error with the app password.

To us, it is not making sense that all other email clients are working with either Cloudron User Account Password or App Password. The only client that won't is the one we have been using with Cloudron for a year and never had issues until now.

Also, I don't think it has anything to do with caching on my Microsoft account as I am not the only one with this issue I have tried it on others who are facing the same issue and they have their own Microsoft accounts and some their own devices.

@jdaviescoates

Sorry, that was a miscommunication on my part. I personally not known about App Passwords being available. Never had to use it until this week.

I only found out about the feature due to Outlook saying the need for an App Password may be needed.

@fbartels We already know about that and I set up the settings manually as stated in a previous response we tried both authentication methods SSL and StartTLS and neither worked. You can only do that from the more settings page.

I did not screenshot that part as I had already said it was working before we upgraded to cloudron 8.3.0.

Also Outlook auto fetches the correct settings for connecting to the mail server as I have checked and triple checked.

@nebulon No none, not even a failed authentication, normally when an account is logged into I noticed on Cloudron that it lists successful logins etc but nothing when trying to connect from Outlook.

@andreasdueren IMAP as it has always worked up till Cloudron 8.3.0

Generally going by the settings provided in cloudron.

We have also tried both SSL and StartTLS made no difference.

@BrutalBirdie

It's not that confusing,

I had my Outlook on my laptop connected to cloudron mail server, I upgraded to cloudron 8.3.0 and had to reconnect my Outlook. Since then I have been trying to;

1. Connect to the mail server on Cloudron via Outlook.
2. I have tried both the normal Cloudron password method that worked perfectly fine on Cloudron 8.2.9 before Cloudron 8.3.0 and the App Password neither is letting Outlook connect to the mail server on my Cloudron.

The App passwords work for most mail clients but not Outlook and when I use my normal Cloudron password to connect to the mail server it gives that authentication error on ONLY Outlook, no other clients having issues like Thunderbird (Connects via Cloudron password), Spark Desktop (Only connects with App Password).

I have tried moving my cloudron install to a new server and still same issue on that server so it was not the server must be cloudron and outlook authentication issues as all other clients I have used work fine. Some requiring App password as mandatory for security.

Also like to point out this is why I tried the app password instead of my cloudron account password.

The reason I say it is a cloudron and Outlook issue is that Outlook connects to Gmail, iCloud, and others with no issues, mainly all using App Passwords as service providers are stopping ordinary account passwords from being used.

IS IT POSSIBLE OUTLOOK AS NEW POLICIES NOT ALLOWING FOR STANDARD PASSWORDS TO BE USED WHEN CONNECTING TO MAIL SERVERS?

My cloudron mail server is the only mail service I can't connect on Outlook. And by the way, it is not my laptop as I tried the same on my PC and same issue there.