Search results

Please try the reply #4 and see if it helps.

The mentioned domain's is pointed to 72 .47 .195 .95 IP. is this correct?

Also please make sure your domain is point to new server IP address.

Please try to change the PHP version for this domain. By doing this Plesk will re-write the configuration files for this domain. Also check the "Apache & nginx Settings" for this domain. If you have root access, you can try, #plesk repair web artvietnamgallery.com

Please find and delete or rename the index.html in httpdocs directory.

Thank you Peter. There is this backup directory /etc/httpd/conf/modsecurity.d/rules/tortix.backup/ in every server but only this server having this issue.

Some hosting companies block the outgoing on Port 25. You can not unblock this via the Plesk Firewall. Only the hosting company can do this for you. Please check "Tools & Setting > Mail Server Settings" and if it says the Port 25 is Blocked.

Hi All, Since last week, Apache stopped working randomly with the error message below in the journalctl -u httpd.service Starting The Apache HTTP Server... Thu Nov 02 08:00:58.583389 2023] [so:warn] [pid 1365:tid 139844436576384] AH01574: module unique_id_module is already loaded, skipping...

You can add this to increase the ES_JAVA_OPTS Memory, ES_JAVA_OPTS | -Xms2g -Xmx2g or -Xms4g -Xmx4g, most of the time 2g should be enough. The screenshot is from a ElasticSearch 6.8.3.

The M2 Cron is creating and deleting the indexes. This is the expected behavior of M2. Please refer to System requirements | Adobe Commerce when choosing the correct version of ElasticSearch for M2. Do you use any 3rd party extensions for indexing?

Same Cluster names should not be an issue. Please check if these dockers or the server has been restarted and causing this issue.

In this case, Most probably your ElasticSearch dockers might be running out of ES_JAVA_OPTS Memory. Check the ElasticSearch Docker log as root, #docker logs --tail 100 -f [Doker-ID} You can get the [Doker-ID} with #docker ps Also check, #curl -sS "localhost:9200/_cat/nodes?h=heap*&v" If...

Update the AUM yesterday. Then did, plesk sbin modsecurity_ctl --disable plesk sbin modsecurity_ctl --enable service httpd restart Confirmed the ModSecurity is responding as expected...

@jorge ceballos Thank you. It seems to be keeps happening. After updating the AUM then disabled and enabled ModSecurity. After a day or two logs are empty again. Have you checked your logs again?

@Peter Debik Thank you. I manually updated Automic Rule Set. I can confirm it the the ModSecurity stopped responding to the tests again.

Hi, I'm using ModSecurity with Atomic Basic Rule Set across number of servers. Recently I have noticed the ModSecurity is not responding to any of these test explained this is support article...

Did you find a solution for this? I'm looking for a similar solution for outgoing emails. Thank you.

Hi All, More and more server companies now blocking the Port 25 outgoing. Do we have an extension in Plesk which we can configured only for all outgoing emails? I tried the current Plesk External Email extension but it got me to uninstall the Dovecot as well. What is the best solution for...

In addition to Peter's reply, Please see if this is related to you https://support.plesk.com/hc/en-us/articles/14861542533911-Plesk-websites-return-Apache-error-403-on-May-26-2023-client-denied-by-server-configuration

I didn't read the whole thread. For you last screenshot, try to turn off the ModSecurity and rebuild the configuration. Then turn it back on. I experieced the same issue after this...