Question Who is using version 18.0.70 Update #1 ??

[Kwasi]

Server operating system version

Windows Server 2019

Plesk version and microupdate number

18.0.70 Update #1

I have it installed on a new server. Can't FTP at all. Says "Home Directory inaccessible"
Also getting a warning about disabling ALGS but ALGI is not enabled.


Anyone else have any issues with this version?

Looked at so much stuff comparing it to another server in the UK and that one with 18.0.69 Update #4 has been just fine for years.

They are virtually identical, but can't ftp into 18.0.70 server.

 

[Sebahat.hadzhi]

Hello, @Kwasi . Please check if this helps:

https://support.plesk.com/hc/en-us/articles/12376963963415-Can-t-connect-via-FTP-530-User-cannot-log-in-home-directory-inaccessible

 

[Kwasi]

Did that in one of my many steps trying to solve this.

All good. Everything checks out.
Diff between the new server and the older one that has no issues is the Plesk version number.
Compared settings on both

 

[Adhost]

We are using Plesk 18.0.70 on two windows servers and we have an issue with logging in to all Umbraco sites on the server resulting in the website going to 503 error.

In Plesk and in the IIS pool settings it says that the IIS pool was stopped but not by Plesk.

The error is not on a server using 18.0.69 where we are able to log in to the Umbraco sites.

Anyone have any suggestions?

 

[Sebahat.hadzhi]

@Adhost , kindly open a new thread for the issue you are experiencing. The one reported and discussed in this thread is related to FTP. As far as I understand, your issue is quite different.

 

[HartleysKid]

Hi @Adhost, Plesk 18.0.70 update #2 has just been installed on our server and all 4 Umbraco websites are experiencing same issue (we use 2 completely different versions of Umbraco also). Did you manage to find a solution to this please?

 

[Adhost]

Hi @HartleysKid . Yes we did. Plesk support helped.

So they asked us to deactivate a rule in mod security which did not work. Here was what they wrote:

"Therefore I would ask you to navigate to Tools & Settings -> Web Application Firewall (ModSecurity) and deactivate OWASP_CRS/ATTACK-GENERIC"

It gave an error in the Web Application Firewall (ModSecurity) page and I replied with that error and got this reply again:

"This behavior is unexpected. The error means database inconsistency.Let me ask you to apply a solution from this article:
https://support.plesk.com/hc/en-us/articles/12377799486615

1. Connect to the Plesk server via RDP.
2. Start a command prompt as an Administrator.
3. Create a Plesk database dump:
4. plesk db dump psa > C:\psa_dump.sql
5. Repair the Plesk database:
6. plesk repair db -y
7. Open the Plesk database in MySQL:
8. plesk db
9. Remove the orphaned entries:
10. DELETE i, ia FROM IisAppPools i LEFT JOIN IisAppPoolDomains ia ON i.id = ia.poolId LEFT JOIN domains d ON d.id = ia.domainId WHERE d.name IS NULL AND i.id != 1;
11. Log in to Plesk.
12. Go to Tools & Settings > Web Application Firewall (ModSecurity), and click OK to update/activate the rule-set.
13. Note: If the error message is still shown, select another rule-set and apply the changes. Then switch back to previous rule-set.

Let us know if it helped to change the behavior or assistance is required with applying the solution.
Best regards,
Ivan Postnikov
Support Team Leader"

 

[HartleysKid]

Hi @HartleysKid . Yes we did. Plesk support helped.

So they asked us to deactivate a rule in mod security which did not work. Here was what they wrote:

"Therefore I would ask you to navigate to Tools & Settings -> Web Application Firewall (ModSecurity) and deactivate OWASP_CRS/ATTACK-GENERIC"

It gave an error in the Web Application Firewall (ModSecurity) page and I replied with that error and got this reply again:

"This behavior is unexpected. The error means database inconsistency.Let me ask you to apply a solution from this article:
https://support.plesk.com/hc/en-us/articles/12377799486615

1. Connect to the Plesk server via RDP.
2. Start a command prompt as an Administrator.
3. Create a Plesk database dump:
4. plesk db dump psa > C:\psa_dump.sql
5. Repair the Plesk database:
6. plesk repair db -y
7. Open the Plesk database in MySQL:
8. plesk db
9. Remove the orphaned entries:
10. DELETE i, ia FROM IisAppPools i LEFT JOIN IisAppPoolDomains ia ON i.id = ia.poolId LEFT JOIN domains d ON d.id = ia.domainId WHERE d.name IS NULL AND i.id != 1;
11. Log in to Plesk.
12. Go to Tools & Settings > Web Application Firewall (ModSecurity), and click OK to update/activate the rule-set.
13. Note: If the error message is still shown, select another rule-set and apply the changes. Then switch back to previous rule-set.

Let us know if it helped to change the behavior or assistance is required with applying the solution.
Best regards,
Ivan Postnikov
Support Team Leader"

Hi @Adhost, Thank you for taking the time to reply. This is very much appreciated. Deactivating OWASP_CRS/ATTACK-GENERIC resolved the issue. I can now log into my Umbraco websites!

 

[Adhost]

Hi @Adhost, Thank you for taking the time to reply. This is very much appreciated. Deactivating OWASP_CRS/ATTACK-GENERIC resolved the issue. I can now log into my Umbraco websites!

Great! Happy that it helped You as well.