Live Helper Chat support forum.. Forum is locked. New place for questions - Github Discussions
You are not logged in.
Pages: 1
Hi,
I installed the Live Helper Chat (Laravel version: h t t p s://github.com/LiveHelperChat/livehelperchat_laravel ) and followed the istruction, but in Widget embed code (new) i get "from origin '***' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource." error. i used the suggested .htaccess under the lhc_web directory. also convert/change/add .htaccess settings to web.config but seems there is a conflict here. (IIS pointed to laravel public folder and other livehelperchat_laravel insatllation instructions followed)
any idea to resolving this issue would be appreciated
Last edited by 1010 (2022-02-11 18:34:21)
Offline
Hi, welcome on LHC Forum.
You can read the following post: https://forum.livehelperchat.com/viewtopic.php?id=2195
Also: https://doc.livehelperchat.com/docs/int … her-domain
PeopleInside - Live helper chat - free limited forum support!
For commercial support or GitHub [see FAQ here]
If you want to support this open source project, just donate [see support page]
Something wrong with the forum? [contact a superhero]
Offline
Thank you Admin for your quick response. i have read above suggestion and tried them. let me ask my question in another way. does even .htaccess call by LHC routes on Windows server when IIS manage web server routes? because seems when your web server is IIS, the .htaccess files won't call. ( i added some redirect rules in .htaccess and they didnt work)
Offline
I'm sorry but I just know Linux for the servers
PeopleInside - Live helper chat - free limited forum support!
For commercial support or GitHub [see FAQ here]
If you want to support this open source project, just donate [see support page]
Something wrong with the forum? [contact a superhero]
Offline
For nginx and apache https://github.com/LiveHelperChat/liveh … f_examples related config have to be applied. How to get it working under IIS and add CORS header requirement that's your part to solve.
Offline
Just for anyone who may have this problem. if your web server is IIS and have your LHC application in subfolders (like LHC in Laravel) then in IIS you need to convert livehelperchat\lhc_web folder to an application. and convert lhc .htaccess to web.config equivalent for this new application, this way IIS knows to handle the LHC routes with child web.config not parent application/site web.config.
Offline
For anyone else who may encounter the same issue, it appears that the IIS on the remote server was missing this module.
Offline
Pages: 1