Search results

I haven’t personally used Hetzner Cloud. However, the usual process is to purchase an additional IP from your hosting provider and then add it to Plesk by going to: Tools & Settings > IP Addresses If you plan to use the new IP for a Name Server, it is recommended to use an IP address in a...

Thank you very much for the report! It will save me a lot of time, as I'm also using the Plesk one-click auto installer. Did you use the following command? sh <(curl https://autoinstall.plesk.com/one-click-installer || wget -O - https://autoinstall.plesk.com/one-click-installer)

This step may also be required if you choose Option 1. For instructions, please refer to the following link: https://www.godaddy.com/en-au/help/add-custom-hostnames-12320

It appears that you are not using custom name servers for your domain registrar (I believe you are using GoDaddy). You have two options to resolve this: Option 1: Update your domain registrar’s name servers to the following: ns1.incontri-escort.it ns2.incontri-escort.it Once you make this...

I tried the PHP script below. <?php echo "<pre>"; echo "PHP Version: " . phpversion() . "\n"; echo "Session Save Path: " . ini_get('session.save_path') . "\n"; try { if (session_status() !== PHP_SESSION_ACTIVE) { session_start(); echo "Session started successfully.\n"...

How about if you, #ls -lha in /Maildir/.INBOX Do you see any large files?

I think in the Sender Score they are referring to the reverse DNS (PTR) associated with your IPs. To check this, you can use a website like DNS Propagation Checker - Global DNS Checker Tool . Simply enter your IP address, select 'PTR', and see if it resolves to bounceout05.ispgateway.de or...

Sorry, as you can understand, it would be a bit difficult to comment on this without seeing the custom PHP script. Also, have you checked the FTP log on the remote server when this issue occurs?

Is this a custom PHP script?

Since you mentioned that this issue occurs intermittently, have you considered scenarios such as the server attempting to resolve the hostname via IPv6, while your FTP server may not support IPv6?

I'm glad I could help. By checking the Fail2Ban logs, you can determine why the IP was added to Fail2Ban in the first place and take appropriate action.

For example, if you are currently trying to connect to the server using your home or office internet and receiving a connection refused error, you can try connecting using your mobile device with a mobile data connection. Then navigate to the Fail2Ban and remove the home or office internet...

I was able to connect to your IP via SSH on port 22 without any issues. It seems that, for some reason, your local public IP has been added to Fail2Ban. Try connecting to your server using a different network with a different IP then remove your IP from the Fail2Ban

In addition to Raul's answer, this can happens if you are using older version of Apache as well. You can try, #httpd -v and see if the Apache version is above 2.2

As the root user, if you try: #plesk login What URL(s) are displayed there? I have noticed that the "This site can't be reached" error shows one URL, while the error message contains a different URL.

I think in this case, it is best to use the Plesk Migrator. https://docs.plesk.com/en-US/obsidian/migration-guide/migrating-from-supported-hosting-platfoms/migrating-via-the-plesk-interface.75721/

Glad to hear you have resolved your issue. I'm not sure what really happened. These services should have been enabled on reboot by default.

I think you should be running Postfix for SMTP. You can make sure this by visiting 'Tool & Settings > Mail Server Settings' Try, #systemctl status postfix after a reboot and make sure the service is running.

Try, #systemctl is-enabled dovecot If it is returning 'disabled', enable it on the reboot. #systemctl enable dovecot To me it is look like it disabled on the reboot. '/usr/lib/systemd/system/dovecot.service; disabled;'

@BjornTheBassist, I completely understand the frustration. Have you considered the possibility of a Noisy Neighbor? I had a similar experience due to a Noisy Neighbor. I couldn't find any issues with my VM—everything appeared normal in terms of CPU and memory usage—but sometimes the websites...