Search results

Thank you for your reply! Yes, the plesk.page sites are only temporary and internal. I waited until the sites disappeared again and checked with DNS tools: There was no entry on the NS. Changing the IP address from the Plesk backend was not possible, because it was in use by an active session...

Now the problem reappeared. It looks like some information at the nameservers expires and is not updated automatically. Firefox says "Hmm. We’re having trouble finding that site. We can’t connect to the server at abc-def.51-38-52-181.plesk.page." The developer tools of the browser also mention...

I changed now the DNS settings, disabling the local DNS service, which brought the sites back. Keeping fingers crossed ...

Update: After the update to 18.0.70 #4 even plesk repair dns doesn't seem to help. Sites remain offline.

After an automatic update to 18.0.70 Update 2 all sites were inaccessible. We managed to recover them with plesk repair dns, particularly "Restore the user DNS configuration file from the template? [Y/n] Restoring the user DNS configuration file" seems to have helped. Now, however, it happened...

Thank you! Indeed, it works now after I moved that line into a bash script and call that script in the event.

I want to set up notifications for any user login (including admin/root) to Plesk using this information: Question - Plesk email alert login So I created an event "Plesk user logged in" with the command echo "username: ${NEW_CONTACT_NAME}" | mail -s "Plesk: User login" -r "no-reply@example.com"...