• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Issue Docker + Varnish - Reboot Mystery

pr0tax

New Pleskian
Hello,

I followed the Plesk/Varnish tutorial on here with Docker and it works a charm. I continued to apply some other updates to the server afterwards, then I did a reboot and everything went horribly wrong. Luckily I had a snapshot available, but I didn't need it in the end.

The conclusion is (TLDR), when I reboot the server, it just throws up a whole load of 503 backend errors.

The fix was for me to run the last couple of steps everytime I reboot the server:

docker ps | grep varnish | awk {'print $1'} | xargs -i docker exec -t {} sed -i '/.port/c\ .port = "7080";' /etc/varnish/default.vcl

and

docker ps | grep varnish | awk {'print $1'} | xargs -i docker exec -t {} sed -i '/.host/c\ .host = "203.0.113.2";' /etc/varnish/default.vcl

With my server IP in the second command. After this, I reboot the container and all works again perfectly.

It seems as though something is missing when rebooting the server, as I have to repeat this process everytime... am I best just installing and configuring Varnish on the actual server or is there something I'm missing?

N.B - I have tried it with both "Automatic start after system reboot" on and off...
 
Back
Top