Search results

Hello, plesk in docker should not be used in a production environment or for production purposes. It designed for integration (mainly API) testing and quick features overview without necessary VPS delegation and installation of a stand-alone product.

You mean REST API currently is not has many functions? It is :( Unfortunately i can not. BTW i think you can feet your needs with cli methods (except one that give options list)

Hello, adding headers to the front proxy (nginx) is preferred (single responsibility). But i suppose adding headers to apache should work too.

Hi, @Jelle_Timmer Unfortunately we can not synchronize internal plesk SDK between different releases. Method which provide CLI options info uses JSON formatter available since 17.9 (now known as 18.0 Obsidian). You can anyway use CLI commands interface to execute commands in 17.8. If you need...

You are welcome. Feel free to ask again if have more troubles.

First one is included into /etc/apache2/plesk.conf.d/server.conf (or /etc/httpd/... on centos/rhel) Second one is just Off by default and not included anywhere. You can override any global settings adding your into the end of /etc/apache2/apache2.conf file and then you need to restart apache

Hello, you need to use ip other then localhost or 127.0.0.1. You can't use there IPs because mysql clients routes this requests to local socket and you can not change this (and there are no mysql socket inside your perl container). You can share socket between containers using volumes but i...

Additionals headers for apache can be added using Apache & nginx Settings > Apache > Additional headers. Just add headers one by one on new string each like this X-XSS-Protection: "1; mode=block" X-Content-Type-Options: nosniff Strict-Transport-Security: "max-age=63072000; includeSubdomains;"...

Can you use repair tool in CLI? Type 'plesk repair all -y' and check is it help.

This error can be occured when php-fpm server is restarting when new configuration applied. You also can try increasing php resources in Domain > PHP Settings > Set pm.max_children to 10 or 20, pm.max_requests to 1000, pm to dynamic. Switching from unix socket is not a good solution (because...

Do you try press Check for updates button. It may invalidate cache and possibly reread actual updates.

Hello, nginx using it's own caching. You can read more in official doc: NGINX Docs | NGINX Content Caching

Hello, you can read this documents to learn how upgrade plesk to latest version: - Upgrading Plesk Using Administrator GUI - How to upgrade Plesk to the next release PS Keep plesk on latest version is a good decision which may solve lot's of problems. Also i can recommend to enable auto updates...

Can you please give URl of site you experienced problem with (You can send it to me using PM). I would like to check problem more precisely. Also you can do something on your own: 1. Trying full reconfiguration plesk sbin httpdmng --reconfigure-all 2. Test web server listening 443 port netstat...

Thanks for reply, @Tchiboun Because plesk 17.0 is really outdated today i can propose two solutions to achieve quick result: - Update to latest stable 17.8 version and get all updates and bug fixes OR - Contact plesk support directly. I suppose this problem can be mitigated effectively only...

Hello, @Tchiboun Let's start from beginning. Can you please execute plesk version in CLI and copy-paste result as is. Please, also provide info about your server OS name and OS version. Then we can continue investigation.

Okay, i tested it on my deb9 plesk added your config to nginx.conf server { listen localhost:61709; location / { stub_status on; access_log off; allow 127.0.0.1; deny all; } } Check nginx -t nginx: the configuration file /etc/nginx/nginx.conf syntax is ok nginx...

i will research this topic. Can you confirm that goal is to serve static files by nginx cache without requests to apache?

I suppose reading this topic will give you an idea Cannot run command as www-data using su

http://nginx.org/en/CHANGES localhost on modern OSes resolves to 127.0.0.1 and ::1 and using hostname instead of IP address gives you this error PS This is only idea, i'm not sure. Also you can use nginx -T > full.conf to compile full nginx config (with all includes) and check for duplicates