Resolved: UMC not accessible under FQDN

UCS - Univention Corporate Server
#1

After installation of Univention 5.0 using the UCS-Installation-amd64.iso on a fresh VMware Workstation VM univention management console is accessible und fully functional under https://ucshost/univention/umc/#/

However, under https://ucshost.my.fqdn/univention/umc/#/ I get an 404 not found from nginx

I want to use the full URL (ucshost.my.fqdn) as I am using my wildcard certificate for *.my.fqdn

Installation of my wildcard certificate by doing ucr set apache2/set/certificate etc. seems to be ok, as apache2 restarted without complaints, and presents my wildcard certificate when accessing https://ucshost - but this does not match my wildcard certificate for *.my.fqdn

What is necessary to get access to UMC under https://ucshost.my.fqdn/univention/umc/#/ ?

#2

This error was due to caching issues. Opening the URL https://ucshost.my.fqdn/univention/umc/#/ in another incognito browser worked without issues.

P.S.: Browser with problems was Firefox, specifically with activated DNS over https. This caused Firefox to resolve ucshost.my.fqdn to my root server’s public IP, instead of honoring my local hosts file. After adding an exception in Firefox’s DNS settings for ucshost.my.fqdn, and clearing the cache for ucshost.my.fqdn I now can access UMC as expected using the full fqdn URL

Mastodon