• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved Removing Cookie Site

FlareCO

FlareCO

New Pleskian
Hey Plesk,

how i can remove the Cookie Site.

its set a random cookie with "hasSiteVisit".

I tried to reinstall Plesk but the problem doesnt dissapear.

I need to remove it for a Survey Provider called Personaly they send a Postback but they use a no cookie system.
everytime the Postback comes it get blocked by Plesk via the ****ing cookie site.
 
Visit: view-source:cryptohydra.net


or
HTML: 
<html> <head><meta http-equiv="refresh" content="1" /><meta http-equiv="cache-control" content="max-age=0" /><meta http-equiv="cache-control" content="no-cache" /><meta http-equiv="expires" content="-1" /><meta http-equiv="expires" content="Tue, 01 Jan 1980 1:00:00 GMT" /><meta http-equiv="pragma" content="no-cache" /></head> <script type="text/javascript"> <!-- function getCookie(w){ cName = ""; pCOOKIES = new Array(); pCOOKIES = document.cookie.split('; '); for(bb = 0; bb < pCOOKIES.length; bb++){ NmeVal = new Array(); NmeVal = pCOOKIES[bb].split('='); if(NmeVal[0] == w){ cName = unescape(NmeVal[1]); } } return cName; } function printCookies(w){ cStr = ""; pCOOKIES = new Array(); pCOOKIES = document.cookie.split('; '); for(bb = 0; bb < pCOOKIES.length; bb++){ NmeVal = new Array(); NmeVal = pCOOKIES[bb].split('='); if(NmeVal[0]){ cStr += NmeVal[0] + '=' + unescape(NmeVal[1]) + '; '; } } return cStr; } function setCookie(name, value, expires, path, domain, secure){ var vlad = name + "=" + escape(value); if(expires){ expires = setExpiration(expires); vlad += ";expires=" + expires; } if(path){ vlad += ";path=" + path; } if(domain){ vlad += ";domain=" + domain; } if(secure){ vlad += ';secure'; } document.cookie = vlad; } function setExpiration(cookieLife){ var today = new Date(); var expr = new Date(today.getTime() + cookieLife * 24 * 60 * 60 * 1000); return expr.toGMTString(); } function delete_cookie(name){ document.cookie = name +'=; Path=/; Expires=Thu, 01 Jan 1970 00:00:01 GMT;'; } // --> </script> <script type="text/javascript"> <!-- delete_cookie('hasVisitedSite'); setCookie('hasVisitedSite', 'Yes', '3', '/', '300', ''); delete_cookie('fb624561f4f8b25819e9b3c4fad70f85'); setCookie('fb624561f4f8b25819e9b3c4fad70f85', 'Yes', '3', '/', '300', ''); --> </script><body></body></html>


then you see a cookie will be placed and the header is refreshing.
 
Last edited:
The content of your website has nothing to do with Plesk. To remove the cookie entries, you need to edit the website source files or scripts. This is completely independent from a Plesk installation or environment.
 
The Problem is, its from Plesk.

In the newest Version it will be added.
Since i upgraded to a new Plesk Version i get this Cookie Site.
 
Assuming you installed Nginx during the update. It's not "Plesk", It's that you added Nginx to the mix as a reverse proxy.

rbf8kg.jpg
 
Tools & Settings > Services Management

Stop Nginx, this will throw Apache back onto Port 80 and HOPEFULLY that should resolve it.
 
Mark Muyskens said:
I don't see that in the source of cryptohydra.net;


2pzl2tj.png
Click to expand...
root@vps-zap325816-1:~# plesk
Usage: plesk [command]

Commands:
bin - Run the specified Plesk command-line utility (e.g., domain, client)
conf - Open the specified Plesk configuration file in the editor
daily - Run daily maintenance script
db - Database related commands. Open MySQL console by default.
ext - Call a command-line interface of the specified Plesk extension
help - Show help and exit
installer - Parallels Installer shortcuts and command completion
log - Open the specified Plesk configuration file in the editor
login - generate login link for specified user
php - Run a PHP script using the Plesk PHP interpreter
repair - Check and repair Plesk
sbin - Run the specified Plesk internal utility
version - Show product version information
root@vps-zap325816-1:~# service nginx
[info] Usage: nginx {start|stop|restart|reload|force-reload|status|configtest|up grade|reopen}.
root@vps-zap325816-1:~# service nginx status
● nginx.service - Startup script for nginx service
Loaded: loaded (/lib/systemd/system/nginx.service; disabled)
Active: inactive (dead)
root@vps-zap325816-1:~# service nginx stop
root@vps-zap325816-1:~# service nginx status
● nginx.service - Startup script for nginx service
Loaded: loaded (/lib/systemd/system/nginx.service; disabled)
Active: inactive (dead)

Mar 05 18:25:59 vps-zap325816-1.zap-srv.com systemd[1]: Stopped Startup script for nginx service.
root@vps-zap325816-1:~# service nginx stop
root@vps-zap325816-1:~# service nginx stop
root@vps-zap325816-1:~# service nginx stop
root@vps-zap325816-1:~# service nginx stop
root@vps-zap325816-1:~# service nginx stop
root@vps-zap325816-1:~# service nginx stop
root@vps-zap325816-1:~# service nginx stop
root@vps-zap325816-1:~# service nginx status
● nginx.service - Startup script for nginx service
Loaded: loaded (/lib/systemd/system/nginx.service; disabled)
Active: inactive (dead)

Mar 05 18:25:59 vps-zap325816-1.zap-srv.com systemd[1]: Stopped Startup script for nginx service.
Mar 05 18:26:49 vps-zap325816-1.zap-srv.com systemd[1]: Stopped Startup script for nginx service.
Mar 05 18:26:50 vps-zap325816-1.zap-srv.com systemd[1]: Stopped Startup script for nginx service.
Mar 05 18:26:50 vps-zap325816-1.zap-srv.com systemd[1]: Stopped Startup script for nginx service.
Mar 05 18:26:51 vps-zap325816-1.zap-srv.com systemd[1]: Stopped Startup script for nginx service.
Mar 05 18:26:51 vps-zap325816-1.zap-srv.com systemd[1]: Stopped Startup script for nginx service.
Mar 05 18:26:52 vps-zap325816-1.zap-srv.com systemd[1]: Stopped Startup script for nginx service.
Mar 05 18:26:52 vps-zap325816-1.zap-srv.com systemd[1]: Stopped Startup script for nginx service.
root@vps-zap325816-1:~# service nginx status
● nginx.service - Startup script for nginx service
Loaded: loaded (/lib/systemd/system/nginx.service; disabled)
Active: inactive (dead)

Mar 05 18:25:59 vps-zap325816-1.zap-srv.com systemd[1]: Stopped Startup script for nginx service.
Mar 05 18:26:49 vps-zap325816-1.zap-srv.com systemd[1]: Stopped Startup script for nginx service.
Mar 05 18:26:50 vps-zap325816-1.zap-srv.com systemd[1]: Stopped Startup script for nginx service.
Mar 05 18:26:50 vps-zap325816-1.zap-srv.com systemd[1]: Stopped Startup script for nginx service.
Mar 05 18:26:51 vps-zap325816-1.zap-srv.com systemd[1]: Stopped Startup script for nginx service.
Mar 05 18:26:51 vps-zap325816-1.zap-srv.com systemd[1]: Stopped Startup script for nginx service.
Mar 05 18:26:52 vps-zap325816-1.zap-srv.com systemd[1]: Stopped Startup script for nginx service.
Mar 05 18:26:52 vps-zap325816-1.zap-srv.com systemd[1]: Stopped Startup script for nginx service.
root@vps-zap325816-1:~# service nginx status
● nginx.service - Startup script for nginx service
Loaded: loaded (/lib/systemd/system/nginx.service; disabled)
Active: inactive (dead)

Mar 05 18:25:59 vps-zap325816-1.zap-srv.com systemd[1]: Stopped Startup script for nginx service.
Mar 05 18:26:49 vps-zap325816-1.zap-srv.com systemd[1]: Stopped Startup script for nginx service.
Mar 05 18:26:50 vps-zap325816-1.zap-srv.com systemd[1]: Stopped Startup script for nginx service.
Mar 05 18:26:50 vps-zap325816-1.zap-srv.com systemd[1]: Stopped Startup script for nginx service.
Mar 05 18:26:51 vps-zap325816-1.zap-srv.com systemd[1]: Stopped Startup script for nginx service.
Mar 05 18:26:51 vps-zap325816-1.zap-srv.com systemd[1]: Stopped Startup script for nginx service.
Mar 05 18:26:52 vps-zap325816-1.zap-srv.com systemd[1]: Stopped Startup script for nginx service.
Mar 05 18:26:52 vps-zap325816-1.zap-srv.com systemd[1]: Stopped Startup script for nginx service.
root@vps-zap325816-1:~# service nginx.service status
● nginx.service.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
root@vps-zap325816-1:~# service nginx.service stop
Failed to stop nginx.service.service: Unit nginx.service.service not loaded.
root@vps-zap325816-1:~# service nginx stop
root@vps-zap325816-1:~# /usr/local/psa/admin/sbin/nginxmng -d
root@vps-zap325816-1:~# /usr/local/psa/admin/sbin/nginxmng -s
Disabled
root@vps-zap325816-1:~#

any other idea ?
 
You must log in or register to reply here.

Similar threads

V
Issue Smarthost + SRS = relay?
Replies
2
Views
788
vanlier
V
M
Issue No Domain Reachable when nginx enabled
Replies
11
Views
6K
mvstns
M
kaw.one
Question (VPS) Cloudflare, Gmail and Other Plesk Panel 8443 (2 minutes - slow read)
Replies
1
Views
1K
kaw.one
kaw.one
J
Issue PHP JIT not enabling with plesk performance booster
Replies
6
Views
940
JohnWest
J
P
Resolved PLESK 18.0.60 Problems to configure mails / Certificates, etc.
Replies
8
Views
773
mow
M
Back
Top