>From the logs the auth seems fine. Then it's very strange because it returns 
>500 but there are no errors or exceptions in your log. Could you give me your 
>sogo.conf (hide the passwords/secrets in it) ?

Cheers,
-- 
Quentin Hivert || Alinto || R&D Lead Developer 
19 Quai Perrache 69002 Lyon
www.alinto.com

-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of "Oli Z."
Sent: mardi 23 décembre 2025 15:27
To: [email protected]
Subject: Re: [SOGo] Debian 13 / SOGo / 500 error

Thats my view:
MariaDB [postfixadmin]> describe sogo_mailbox;
+------------+--------------+------+-----+---------+-------+
| Field      | Type         | Null | Key | Default | Extra |
+------------+--------------+------+-----+---------+-------+
| c_uid      | varchar(255) | NO   |     | NULL    |       |
| c_name     | varchar(255) | NO   |     | NULL    |       |
| c_cn       | varchar(255) | NO   |     | NULL    |       |
| mail       | varchar(255) | NO   |     | NULL    |       |
| c_password | varchar(255) | NO   |     | NULL    |       |
+------------+--------------+------+-----+---------+-------+
5 rows in set (0,004 sec)

when i do a select on it i get:

| [email protected]         | [email protected]         | Test Account  
  | [email protected]         | {SHA512-CRYPT}$6$m6wJGw/xxx0

 From the documentation, i see no domain field for viewUrl. So i assume 
thats not mandatory?

Am 23.12.25 um 15:19 schrieb Oli Z.:
> I created the view as described in the documentation, thats what is in 
> use:
>
> viewURL = "mysql://xxx:[email protected]:3306/postfixadmin/sogo_mailbox";
>
> But Sogo still requires a DB, to store data, e.g. calendar 
> information. And i prefer postgre, thats why i have:
> SOGoProfileURL = 
> "postgresql://[email protected]:5433/sogo/sogo_user_profile";
> OCSFolderInfoURL = 
> "postgresql://[email protected]:5433/sogo/sogo_folder_info";
> OCSSessionsFolderURL = 
> "postgresql://[email protected]:5433/sogo/sogo_sessions_folder";
> OCSEMailAlarmsFolderURL = 
> "postgresql://[email protected]:5433/sogo/sogo_alarms_folder";
> OCSAdminURL = "postgresql://[email protected]:5433/sogo/sogo_admin";
>
> As mentioned, the sql auth works like a charm, but SOGo somehow fails 
> _after_ authentication. From the log, i assume it should load some 
> sort of calendar information or so.
>
> I can paste the full config if required.
>
> Am 23.12.25 um 12:32 schrieb Washington Odhiambo ([email protected]):
>>
>>
>> On Tue, Dec 23, 2025 at 2:02 PM "Oli Z." <[email protected]> wrote:
>>
>>     I am not exactly sure what you mean. My users are in mariadb, the
>>     database is called "postfixadmin" because i set this email server up
>>     about 15 years ago and did not know that its a bad idea to call
>>     the db
>>     like the product thats in use :D
>>
>>
>> Who said that it's a bad idea to call the db like the product that's 
>> in use??
>>
>>     I have about 7 users (friends). Next time i would call it
>>     "mailbox_users" or so. Anyway... i followed this guide
>> https://www.sogo.nu/files/docs/SOGoInstallationGuide.html#Authentication-using-SQL
>>
>>     and the authentication works. When i log in to SOGo, it shows a 
>> green
>>     splash with my name, and then the white page appears. So
>>     authentication
>>     against SQL works. But i did not run any other SQL to populate the
>>     SOGo DB.
>>
>>
>> You actually do NOT need the SOGo DB!
>> If you had an existing database with your users, it should have been 
>> easier to create a view of your existing tables for use with SOGo.
>> For example, with Mariadb, for postfixadmin, I used: 
>> https://narkive.com/gJeHppYI.4
>>
>>     I was not aware that anything like this is required. Thats why
>>     i migrated this mysql sql script to postgresql so that i have at
>>     least the
>>     sogo_user_profile table. I have the feeling there is a lot missing
>>     in the documentation... or i am blind. Or both 😉
>>
>>     Maybe something in the log shows something that i dont see, which
>>     might be a problem or relevant.
>>
>>
>> Once you create the VIEW, you just configure SOGo with the DB 
>> details, using the VIEW as the table.
>>
>>
>>
>>
>>
>> -- 
>> Best regards,
>> Odhiambo WASHINGTON,
>> Nairobi,KE
>> +254 7 3200 0004/+254 7 2274 3223
>>  In an Internet failure case, the #1 suspect is a constant: DNS.
>> "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
>> [How to ask smart questions: 
>> http://www.catb.org/~esr/faqs/smart-questions.html]

Reply via email to