Facebook
Twitter- Server operating system version
- Ubuntu 20.04.4 LTS
- Plesk version and microupdate number
- Plesk Obsidian Version 18.0.44
Hey, we used a PlugIn to create the Staging Area. All the configuration within the PlugIn and the Server are correct, however, we still can't access the Staging Area. This is what my colleague sent me and I am running out of questions.
We use a current Plesk server. This is correctly configured so that the Shopware 6 store is located in httpdocs/ and the web server for the host points to httpdocs/public/, so that the store runs correctly in the frontend. So far, so the standard. If now a new staging environment is created, the folder e.g. staging/ is created in httpdocs/. This is obviously how the PlugIn provides for it. If I now call domain.tld/staging/ etc. in the browser, we get a 404. We have now also tried to put a symlink from httpdocs/public/staging/ to httpdocs/staging/, but this contradicts the security settings, because it is not possible to call publicly what is behind the public root. So we tried it the other way around, and moved the created staging folder to public/ and put a symlink from httpdocs/staging/ to httpdocs/public/staging/. Then we get at least so far in the browser that we get a Phusion Passenger error message. However, not the staging environment either. Via subdomain to the staging folder works, but then we have no more licensed plugins, because it is a different domain. So it does not work either. How should we proceed here? Do you already have a solution for Plesk Server? It is the most used server system in the world and actually it only adheres to security standards.
Thanks
We use a current Plesk server. This is correctly configured so that the Shopware 6 store is located in httpdocs/ and the web server for the host points to httpdocs/public/, so that the store runs correctly in the frontend. So far, so the standard. If now a new staging environment is created, the folder e.g. staging/ is created in httpdocs/. This is obviously how the PlugIn provides for it. If I now call domain.tld/staging/ etc. in the browser, we get a 404. We have now also tried to put a symlink from httpdocs/public/staging/ to httpdocs/staging/, but this contradicts the security settings, because it is not possible to call publicly what is behind the public root. So we tried it the other way around, and moved the created staging folder to public/ and put a symlink from httpdocs/staging/ to httpdocs/public/staging/. Then we get at least so far in the browser that we get a Phusion Passenger error message. However, not the staging environment either. Via subdomain to the staging folder works, but then we have no more licensed plugins, because it is a different domain. So it does not work either. How should we proceed here? Do you already have a solution for Plesk Server? It is the most used server system in the world and actually it only adheres to security standards.
Thanks
