Recent content by drudge

Hi @learning_curve, thanks for your update on this. As far as I understood the problem, I cannot change anything to make it work, right? What is the way to go here? As far as I got it, I could temporarily install and use Firefox because it uses it own cert record set. I typically use the GUI...

To minimize chances it's a matter of my end device, I used the tools of Geocerts which allows to scan the SSL certificate on a custom port. On mydomain.tld:8443, everything looks fine: However, the tool also complains on mydomain.tld:8447 when the autoupdater is up, running, and scanned...

Hello Nic G, thanks for your ideas. I removed the lines from the panel.ini but this changed not the behaviour. Regarding your question 2, yes, I indeed use the same browser. This happens on both Chrome and Safari. Logged in on mydomain.tld:8443 (certificate valid) on my MacBook (MacOS Big Sur...

I currently have trouble to secure the Plesk updater which opens at port 8447 when I click "Updates" on the tools and settings page in the Plesk admin panel. I migrated my server from Ubuntu 18.04 to 20.04 using the Plesk Migrator tonight and I'm now on Plesk Obsidian 18.0.39 Update 1...