• 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.

Question nginx and varnish (docker)

andyxyz

Basic Pleskian
Server operating system version
ubuntu 20.04
Plesk version and microupdate number
18.01
Has anyone worked out a method of running pure nginx with varnish? Currently I can run everything with nginx only but the only way I can get varnish running in docker is to point that to 7080 / apache. Can anyone see a way to point varnish to nginx?
 
OK the silence is deafening..

what if I add a new nginx block for a new port (minus the docker proxy block) and point varnish to this port?
 
OK story so far.. this is Magento 2..

So creating a custom nginx block in /etc/nginx/conf.d/ with a copy of the port 80 nginx server block (minus any extension inserts) running on a random port and pointing varnish (default m2 exported vcl) to this works just fine for everything except images. (static content fine.. images.. not fine)
Varnish cant see get.php

other than this one anomaly magento 2 will run even if apache is disabled.

Any ideas?

- ReqURL /get.php

- VCL_call RECV
- VCL_return pass
- VCL_call HASH
- VCL_return lookup
- VCL_call PASS
- VCL_return fetch
- Link bereq 720902 pass
- Timestamp Fetch: 1712222345.680428 3.822114 3.822114
- RespProtocol HTTP/1.1
- RespStatus 404
- RespReason Not Found
- RespHeader Server: nginx
 
Back
Top