I have setup a replica of our live site on our inhouse server to try and resolve our session recording issues. So we can record sessions see how it sworking. I am using the www2 prefix for this. I am getting this error in system check
What is trying to access port 443 ? The site is being served ok on https. It is behind a nginx proxy. Niginx listens on https but site is running on http.
Thanks
Paul
For Session Recording to work, the visitor of the page needs to be able to request https://www2.abc.com/analytics/plugins/HeatmapSessionRecording/configs.php. If this request fails, no sessions (and heatmaps) will be recorded.
Therefore the system check tests if it can request the https://www2.abc.com/analytics/plugins/HeatmapSessionRecording/configs.php file and according to your error fails to do so.
So can you check if you are able to request the URL from your browser correctly. If so maybe only your server isn’t setup to reach itself via HTTPS and therefore only the system check fails even though it should work for your visitors.
Hello Lukas, config.php seems to be accessible I do not get a 404 just a blank page. As I have moved the site from www to www2 do I need to update the tracking code. At moment cannot capture any recordings ?
In my apache log I have
10.10.10.2 - - [26/Mar/2018:11:39:38 +0100] “GET /analytics/plugins/HeatmapSessionRecording/configs.php HTTP/1.0” 400 205 "-"
400 is bad request.
Any idea what may cause this ?
The HyperText Transfer Protocol (HTTP) 400 Bad Request response status code indicates that the server could not understand the request due to invalid syntax.
Just a wild guess, but maybe your server does not speak HTTP/1.0 anymore?
Do you have access to the server? If yes, you could try curl --http1.0 https://www2.abc.com/analytics/plugins/HeatmapSessionRecording/configs.php directly.
I have a location setting in the reverse proxy which should allow the plugins
location / {
proxy_pass http://10.10.1.19;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-Proto $scheme; # very important to avoid the ssl warnings in browser with http backend
client_max_body_size 100m;
}