[horde] H6 new install stuck with web gui access

Brent impuser at bitrealm.com
Thu Mar 6 23:46:53 UTC 2025


  Quoting Andreas Mauser <andreas at mauser.info>:

> Am 6. März 2025 um 22:51 schrieb "Andreas Mauser"  
> <[andreas at mauser.info](mailto:andreas at mauser.info?to=%22Andreas%20Mauser%22%20%3Candreas%40mauser.info%3E)\>:
>
>> Hi and thank you so much for the H6 development.
>>
>> I was successful in installing prerequisites, preparing apache with  
>> minimal vonfig and getting a cert.
>>
>> Also the H6 installation via composer seemed to be successful (it  
>> only complained about cache but completed successfully: Cannot  
>> create cache directory /var/www/.cache/composer/files/, or  
>> directory is not writable. Proceeding without cache. See also  
>> cache-read-only config if your filesystem is read-only.)
>>
>> This is the last step which i was able to do successfully:
>>
>> [https://wiki.horde.org/Doc/Dev/H6/Installation/InstallBase](https://wiki.horde.org/Doc/Dev/H6/Installation/InstallBase)
>>
>> Now I would like to finish the installation via GUI via https, but  
>> get a "Service unavailable" with only this message in the log:
>>
>> wm.domain.com:80 10.x.x.x - - \[06/Mar/2025:22:39:10 +0100\]  
>> "\\x16\\x03\\x01\\x02" 400 488 "-" "-"
>>
>> Or, when accessing via http at least I get a directory listing:
>>
>> wm.domain.com:80 10.x.x.x.x - - \[06/Mar/2025:22:46:25 +0100\] "GET  
>> /icons/unknown.gif HTTP/1.1" 200 473  
>> "[https://wm.domain.com/wm/%22](https://wm.domain.com/wm/%22)  
>> "Mozilla/5.0 (X11; Linux x86\_64; rv:128.0) Gecko/20100101  
>> Firefox/128.0"
>>
>> This is strange as a cert for the domain does exist.
>>
>> What does that mean and where can I solve this?  Ok, I came one  
>> step further, can access the GUI.
>
> But that doesnt look like a GUI, its looks like some kind of listing  
> and clicking on something ends up in a "not found"
>
> I'm a lil stuck here. Can someone guide me the right way please? :)
>
>  

The \x16 is part of a tls handshake. That can happen if your web  
browser is trying to use https, but you server is speaking http. Just  
because you hit https, the web server must be configured to talk https.

brent


More information about the horde mailing list