PeopleInside
Regular Pleskian
Username:
TITLE
CORS stop to working using HTTP 2 Plesk Plesk Obsidian Version 18.0.52
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
Plesk Obsidian Version 18.0.52
Ubuntu 22.04.2 LTS
PROBLEM DESCRIPTION
After updating Plesk Obsidian Version 18.0.51 to Plesk Obsidian Version 18.0.52 I discovered that CORS that I have inserted in Additional Nigix directive for using HTTP 2 are no more working.
This directive has been added for made work the live chat widget (livehelperchat).
Plesk Staff helped me about this issue in the past here: Forwarded to devs - HTTP2 and CORS issues
Now I never had changed server, the live chat application is the same, even revert back database and files to a backup that work before live helper chat update never resolve the issue.
If I turn off HTTP 2 so Nigix the issue is resolved but my server never use HTTP 2
I know the correct CORE settings to insert because Plesk Staff has suggested it and was working until some week ago.
Server has not been changed, live helper chat has not been changed because even restore an old backup never made difference so it's not an issue from Live Helper Chat.
My question would be WHY CORES are no more working for Ngix HTTP 2 when the correct core works in Apache and was working on Ngix HTTP 2 too the last week?
I can think the issue is related to me if I changed something in the server but I don't.
STEPS TO REPRODUCE
In Ngix additional directive I have the code suggested:
See the code and a screenshot here
The live chat is installed at livechat.peopleinside.it
in this directory an .htaccess file redirect to the folder livechat
Nothing changed in this weeks just updated Plesk.
Now I'm asking why the CORS are no more working.
If works in Apache, if I followed also the documentation of the live helper chat app
why I'm unable to use HTTP 2 anymore because the widget chat is not showed?
2023-05-18_23-32-00
ACTUAL RESULT
After updating Plesk seems my live chat widget is no more visible.
I understand that someone can tell me I edited maybe the appplication but I did not.
I just upgraded live helper chat but also restoring an old backup (files and database) never work anymore.
Disabling HTTP 2 made all works so the issue is by Plesk side.
As HTTP 2 is no supported only by Apache but needs Nigix, could you help me to understand why this is not working?
I usually never ask for custom help in this forum, I try to discuss just issues I can have using Plesk, usually the forum are able to help with basic suggestion. In this case all was working and stopped and the issue seems to be not my chat application because restore an old working backup still never work.
EXPECTED RESULT
The CORS directive suggested also from the Plesk Staff should work as always do.
Why works in Apache but now are no more working on Additional Ngix directive?
All was working last week.
ANY ADDITIONAL INFORMATION
- Server has not been changed, it is the same, the only update done was Plesk. I also updated live helper chat but restore all files and database of the application to a working backup never resolve so looks the issue is not in the chat application.
- Disabling HTTP 2 Ngix proxy resolve the issue so this made me think the issue comes from Ngix proxy. I'm sure settings are correct because I never changed. Even the live chat domain still be the same..
I really have no idea why this is causing issue and for this now I'm using the old HTTP 1 protocol.
I hope to figure out why CORS may stop to work.
Sadly Plesk need a proxy to have HTTP 2 this caused the issue in the past but after the help of the staff that explained how should be setup, now I should know how to avoid the past issue.. seems the CORS has stopped to work after some day ago update of Plesk.
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM
Help with sorting out
TITLE
CORS stop to working using HTTP 2 Plesk Plesk Obsidian Version 18.0.52
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
Plesk Obsidian Version 18.0.52
Ubuntu 22.04.2 LTS
PROBLEM DESCRIPTION
After updating Plesk Obsidian Version 18.0.51 to Plesk Obsidian Version 18.0.52 I discovered that CORS that I have inserted in Additional Nigix directive for using HTTP 2 are no more working.
This directive has been added for made work the live chat widget (livehelperchat).
Plesk Staff helped me about this issue in the past here: Forwarded to devs - HTTP2 and CORS issues
Now I never had changed server, the live chat application is the same, even revert back database and files to a backup that work before live helper chat update never resolve the issue.
If I turn off HTTP 2 so Nigix the issue is resolved but my server never use HTTP 2
I know the correct CORE settings to insert because Plesk Staff has suggested it and was working until some week ago.
Server has not been changed, live helper chat has not been changed because even restore an old backup never made difference so it's not an issue from Live Helper Chat.
My question would be WHY CORES are no more working for Ngix HTTP 2 when the correct core works in Apache and was working on Ngix HTTP 2 too the last week?
I can think the issue is related to me if I changed something in the server but I don't.
- Server is the same
- Live Helper Chat has been also restored from an old backup but still not showing the widget
- Disabling Nigix resolve the issue but HTTP 2 is no more in use
STEPS TO REPRODUCE
In Ngix additional directive I have the code suggested:
See the code and a screenshot here
The live chat is installed at livechat.peopleinside.it
in this directory an .htaccess file redirect to the folder livechat
Nothing changed in this weeks just updated Plesk.
Now I'm asking why the CORS are no more working.
If works in Apache, if I followed also the documentation of the live helper chat app
Install Guide | Live Helper chat
Tutorial how to setup Live Helper Chat. You can also use available snapshot on DigitalOcean
doc.livehelperchat.com
why I'm unable to use HTTP 2 anymore because the widget chat is not showed?
2023-05-18_23-32-00
ACTUAL RESULT
After updating Plesk seems my live chat widget is no more visible.
I understand that someone can tell me I edited maybe the appplication but I did not.
I just upgraded live helper chat but also restoring an old backup (files and database) never work anymore.
Disabling HTTP 2 made all works so the issue is by Plesk side.
As HTTP 2 is no supported only by Apache but needs Nigix, could you help me to understand why this is not working?
I usually never ask for custom help in this forum, I try to discuss just issues I can have using Plesk, usually the forum are able to help with basic suggestion. In this case all was working and stopped and the issue seems to be not my chat application because restore an old working backup still never work.
EXPECTED RESULT
The CORS directive suggested also from the Plesk Staff should work as always do.
Why works in Apache but now are no more working on Additional Ngix directive?
All was working last week.
ANY ADDITIONAL INFORMATION
- I know the directive needed for made the live chat widget visible, they are described in the official app documentation here: Install Guide | Live Helper chat , those directive are working in Apache if I turn off HTTP 2 in Plesk so the issue come from the Nigix proxy.
- Additional directive I set in Additional Nigix directive should be correct as it has been suggested here by the team and seems respect what is in Apache. This has stopped to work after Plesk update.
- Server has not been changed, it is the same, the only update done was Plesk. I also updated live helper chat but restore all files and database of the application to a working backup never resolve so looks the issue is not in the chat application.
- Disabling HTTP 2 Ngix proxy resolve the issue so this made me think the issue comes from Ngix proxy. I'm sure settings are correct because I never changed. Even the live chat domain still be the same..
I really have no idea why this is causing issue and for this now I'm using the old HTTP 1 protocol.
I hope to figure out why CORS may stop to work.
Sadly Plesk need a proxy to have HTTP 2 this caused the issue in the past but after the help of the staff that explained how should be setup, now I should know how to avoid the past issue.. seems the CORS has stopped to work after some day ago update of Plesk.
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM
Help with sorting out