Run AMP over subdomain and https certificate from Plesk

[XenoKeks]

OS Name/Version: Debian GNU/Linux 10 (buster)

Product Name/Version: AMP Release “Halimede” - v2.4.0.10, built 27/10/2022 18:15

Problem Description:

Good day,
I installed your software on my server today.
But first of all without the NGINX or the https setting, since I run my dedicated server via the Plesk system.
Now I wanted to ask - before I buy a license - whether it is possible to install (or set up) the AMP in such a way that I create a subdomain in Plesk and the system can be reached via it?
I don’t care if the webroot files remain in /home/amp/. It would only be important to me that I can use my subdomain via Plesk, because my https certificates also run over it.

Thank you for your replies and have a nice day.

[IceOfWraith]

I haven’t used it myself but others seem to have had success running Plesk with their nginx and then AMP as a subdomain.

[XenoKeks]

Cool thanks for your answer.
But… uhm, is there a way to “automatically” configure AMP for this usecase or should i do it myself?
Because AMPs service will start after every update and i think it will reconfigure AMP to default settings i guess?

[IceOfWraith]

You would manually configure AMP using the install script. Then edit the nginx config file to include AMP. I don’t know how Plesk manages that config file so unsure what it would take to make the settings “stick”.

Setting up secure HTTP (HTTPS) with AMP

[Documentation (2)] There are a number of methods that can be used to set up secure HTTP (HTTPS) within AMP depending on your use case. Note that with AMP Enterprise, use of HTTPS is mandatory. 1. Reverse proxy via nginx (recommended, Linux only) If you use the default getamp.sh setup script to install AMP, and you select the option to set up HTTPS when running that script, AMP installs and configures an nginx reverse proxy and Let’s Encrypt certificate handled by certbot to provide secure …

[Greelan]

I don’t know much about Plesk but it looks like it uses Apache for the frontend (webservers) and nginx for the backend (reverse proxy). Seems to assume that each use case will use both. Not clear whether it will allow just an nginx config alone to proxy AMP’s webserver. If it allows a manual nginx config to be added but still handles the certs, then it could work (the wiki article has the sample nginx server block to include for AMP).

[IceOfWraith]

Yeah, I should clarify in my response you would manually configure AMP and select “No” when asked to setup HTTPS in the install script.