• Plesk Uservoice will be deprecated by October. Moving forward, all product feature requests and improvement suggestions will be managed through our new platform Plesk Productboard.
    To continue sharing your ideas and feedback, please visit features.plesk.com

Recent content by MISHO0o

  1. M

    Issue 502 Bad Gateway | When open update page

    is this will effect on current running websites ?
  2. M

    Issue 502 Bad Gateway | When open update page

    It stuck on loading page but not opening anything
  3. M

    Issue 502 Bad Gateway | When open update page

    do you mean when open https://yoursite:8443 not 8447 ? it opens plesk dashboard
  4. M

    Issue 502 Bad Gateway | When open update page

    Hello, recently i head to this link: https://mywebsite:8443/admin/update/product/ and i get this error page: when i go to Open the repair kit i didn't find any thing abnormal, Disk space is 80% free, services are running normally, i even don't have problem with my website tried to restart...
  5. M

    Issue 403 Error Nginx TLS/SSL

    Thx, it works ♥♥
  6. M

    Issue 403 Error Nginx TLS/SSL

    @Raul A. @Sebahat.hadzhi finally i got the reason. it's from WP toolkit bot protection, i disabled it and works fine can i adjust it or config it or it's just on/off ? also i have a question: - i added an "A" record to open the plesk as a subdomain so the link will be >...
  7. M

    Issue 403 Error Nginx TLS/SSL

    here is the ngnix full Access log:
  8. M

    Issue 403 Error Nginx TLS/SSL

    i have Wordfence and Modsecurity enabled but it's not related to Wordfence i don't know if it's related to modsecurity or not the strange thing is it happens for some transactions not for all, while all transcations uses same callback URL but some of them gives 200 reponse and others gives...
  9. M

    Issue 403 Error Nginx TLS/SSL

    @Sebahat.hadzhi can you help please
  10. M

    Issue 403 Error Nginx TLS/SSL

    Error time: 22:13 log time not have this time
  11. M

    Issue 403 Error Nginx TLS/SSL

    in the mentioned log file there are only warning, and there is nothing about the 403 error
  12. M

    Issue 403 Error Nginx TLS/SSL

    i already did that and the above screenshot from log
  13. M

    Issue 403 Error Nginx TLS/SSL

    Hello, i face this issue for a payment gateway callback URL got 403 error it was working fine before migrating to plesk, so is there a setting should be done in nginx to allow this callback URL ?
  14. M

    Issue Error Code 404 for callback URL

    anyone know how to prevent this as it affects all payment transactions to be completed as the callback URL gices the above error
Back
Top