Recent content by TheColin21

Yeah that was my problem too. Didn't check my used network as I thought Plesk would probably configure it the same for all installations if not explicitely changed by the user. I'd suggest changing the generic workaround to use 172.16.0.0/12 as the source subnet as that's the whole reserved IP...

I have to correct myself: I would favor it, if it worked it did not for me...

This workaround seems favourable to me.

Just to be sure: Are we sure this will be fixed in the next docker release? If not, the problem will just reappear.

I'm surprised you encountered it on #2 - that updated worked flawlessly for me.

I have several containers that I access via nginx proxy rules, they all work. Maybe something you did during your fight caused this additional issue ;)

My Ubuntu 22.04 server updated Plesk from 18.0.67 U2 to 18.0.67 U3 today. A few minutes later my monitoring emailed me about all external hosts being down. I am running CheckMK inside a docker container. I then noticed that all my Docker containers were now unable to communicate outside of my...

No, it's a Let's Encrypt certificate.

Hi, I have a domain "domain1.tld" which (DNS-wise spoken) has the subdomain "cloud.domain1.tld". The subdomain is registered in Plesk as a domain assigned to the webspace of "domain2.tld" as I use it as an alias (without redirection, just pointing to the same directory) to "cloud.domain1.tld"...

A pretty important update: after I removed the ondrej repo and rolled back to 2.4.41 I got the next apache2 update today. Just FYI: my server is running Plesk Obsidian 18.0.38 Update #2 on Ubuntu 20.04.3 (everything is up-to-date from the Ubuntu repos), I use Apache2 as web-server and nginx as...

I removed the ondrej apache repo, removed apache2 and everything that belongs to it and installed version 2.4.41 (I think) from Ubuntu's repo. After this I had to restore my configuration from a plesk backup. Nearly gave me a heart attack.

I just updated run apt upgrade and am facing the same error now. The sock file does exist. I do not how to solve this. Plesk's repair command did not work. Do you have any idea?

Okay, thanks

You're completely right, this will keep all Nextcloud data and configuration. What about my Apache/Nginx/PHP configuration though? That's quite a lot too.

Does that mean, that I can save the contents of " /var/www/vhosts/system/cloud.example1.com" and by restoring it afterwards I get the complete configuration of my domain again?