punkstar69
Forum Replies Created
-
Hello and thanks for your answer mmaunder!
The header sent is:
X-Varnish:·1817241226·1817236706(CR)(LF)
Thanks for the response WCat!
At this moment, we are behind a managed server in which he had no access to the setup of the box, so we cant do such a thing.
Is there an alternative way for Wordfence to bypass this problem?
Forum: Plugins
In reply to: [WordPress Social Login] You cannot access this page directly.I am pasting you the config of my Varnish default configuration file for my domain. There is a section about cookies, i hope this helps you understand the problem as you already know how the plugin cookies work exactly.
# This is a basic VCL configuration file for varnish. See the vcl(7)
# man page for details on VCL syntax and semantics.
#
# Default backend definition. Set this to point to your content
# server.
#
backend default {
.host = “127.0.0.1”;
.port = “81”;
}# Drop any cookies sent to WordPress.
sub vcl_recv {
if (!(req.url ~ “wp-(login|admin)”)) {
unset req.http.cookie;
}if (req.url ~ “^/registration/.*$” || req.url ~ “^/wp-admin/.*$” || req.url ~ “^/my-details/.*$” || req.url ~ “^/profile/.*$” || req.url ~ “^/profile” || req.request == “POST”) {
return (pass);
}# Always cache the following file types for all users.
if (req.url ~ “\.(aif|aiff|au|avi|bin|bmp|cab|carb|cct|cdf|class|css|dcr|doc|dtd|exe|flv|gcf|gff|gif|grv|hdml|hqx|ico|ini|jpeg|jpg|mov|mp3|nc|pct|pdf|png|ppc|pws|swa|swf|txt|vbs|w32|wav|wbmp|wml|wmlc|wmls|wmlsc|xml|xsd|xsl)$”) {
unset req.http.Cookie;
}
}sub vcl_fetch {
set beresp.ttl = 20m;
return(deliver);# Don’t allow static files to set cookies.
if (req.url ~ “(?i)\.(png|gif|jpeg|jpg|ico|swf|css|js|html|htm)(\?[a-z0-9]+)?$”) {
# beresp == Back-end response from the web server.
unset beresp.http.set-cookie;}
# Allow items to be stale if needed.
set beresp.grace = 24h;
}sub vcl_deliver {
if (obj.hits > 0) {
set resp.http.X-Cache = “HIT”;
} else {
set resp.http.X-Cache = “MISS”;
}
}Forum: Plugins
In reply to: [WordPress Social Login] You cannot access this page directly.We are using Varnish.
Is there any exception that we can add for your plugin in order to be working with Varnish?
Thanks for your help, i really appreciate this, as i am in despare and i really like your plugin.
Forum: Plugins
In reply to: [WordPress Social Login] You cannot access this page directly.There is no Website Information in Help & Support Tab.
In diagnostics, i recieve fail in:
PHP Sessions are not working correctly or this page has been accessed directly.
If you see an error “Warning: session_start…”, then there is a problem with your PHP server that will prevent this plugin from working with PHP sessions. Sometimes PHP session do not work because of a file permissions problem. The solution is to make a trouble ticket with your web host.
I have tried altering the path by defining it in wp config and all other files. I tested it by doing a php echo, and it works. All files and folders of plugin and sessionpath are set to 755.
Our nginx configuration is:
server {
# Configure the domain that will run WordPress
listen 8080;
server_name domain.gr http://www.domain.gr;
port_in_redirect off;
server_tokens off;
autoindex off;client_max_body_size 15m;
client_body_buffer_size 128k;# WordPress needs to be in the webroot of /var/www/ in this case
root /var/www/vhosts/domain.gr/httpdocs/;
index index.html index.htm index.php;
try_files $uri $uri/ /index.php?q=$uri&$args;
error_log /var/log/php-fpm/www-error.log;# Define default caching of 24h
expires 86400s;
add_header Pragma public;
add_header Cache-Control “max-age=86400, public, must-revalidate, proxy-revalidate”;# Do not allow access to files giving away your WordPress version
location ~ /(\.|wp-config.php|readme.html|licence.txt) {
return 404;
}# enforce www (exclude certain subdomains)
if ($host !~* ^(www|subdomain))
{
rewrite ^/(.*)$ $scheme://www.$host/$1 permanent;
}# Add trailing slash to */wp-admin requests.
rewrite /wp-admin$ $scheme://$host$uri/ permanent;
# Don’t log robots.txt requests
location = /robots.txt {
allow all;
log_not_found off;
access_log off;
}# Rewrite for versioned CSS+JS via filemtime
location ~* ^.+\.(css|js)$ {
rewrite ^(.+)\.(\d+)\.(css|js)$ $1.$3 last;
expires 31536000s;
access_log off;
log_not_found off;
add_header Pragma public;
add_header Cache-Control “max-age=31536000, public”;
}# Aggressive caching for static files
# If you alter static files often, please use
# add_header Cache-Control “max-age=31536000, public, must-revalidate, proxy-revalidate”;
location ~* \.(asf|asx|wax|wmv|wmx|avi|bmp|class|divx|doc|docx|eot|exe|gif|gz|gzip|ico|jpg|jpeg|jpe|mdb|mid|midi|mov|qt|mp3|m4a|mp4|m4v|mpeg|mpg|mpe|mpp|odb|odc|od$
expires 31536000s;
access_log off;
log_not_found off;
add_header Pragma public;
add_header Cache-Control “max-age=31536000, public”;
}# pass PHP scripts to Fastcgi listening on Unix socket
# Do not process them if inside WP uploads directory
# If using Multisite or a custom uploads directory,
# please set the */uploads/* directory in the regex belowa
location ~* (^(?!(?:(?!(php|inc)).)*/uploads/).*?(php)) {
try_files $uri = 404;
fastcgi_split_path_info ^(.+.php)(.*)$;
fastcgi_pass unix:/var/run/domain.socket;
fastcgi_index index.php;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
include fastcgi_params;
fastcgi_intercept_errors on;
fastcgi_ignore_client_abort off;
fastcgi_connect_timeout 60;
fastcgi_send_timeout 180;
fastcgi_read_timeout 180;
fastcgi_buffer_size 128k;
fastcgi_buffers 4 256k;
fastcgi_busy_buffers_size 256k;
fastcgi_temp_file_write_size 256k;
}# Deny access to hidden files
location ~ /\. {
deny all;
access_log off;
log_not_found off;
}}
# Redirect all www. queries to non-www
# Change in case your site is to be available at “www.yourdomain.tld”
#server {
# listen [::]:8080;
# server_name http://www.yourdomain.tld;
# rewrite ^ $scheme://yourdomain.tld$request_uri? permanent;
#}Please advise, thanks in advance!
Have you found a solution on this ?
WordPress Social Login seems wonderful and we are not about to remove it due to this error.
Forum: Fixing WordPress
In reply to: Dashboard Problem!Yes.
These were my first steps ( deactivating and reactivating one by one and also cleaning inactive )
I tried switching to twenty eleven but the dashboard still remain the same.
I just tried to replace the wp-admin and wp-includes but the problem is still the same.
Forum: Fixing WordPress
In reply to: Dashboard Problem!The url of the website is
If you want me to provide something more, let me know.
Thanks
Forum: Fixing WordPress
In reply to: Dashboard Problem!I guess this would require login details.
Do you need me to paste my dashboard.php code?