However, once I go to wp-admin page and attempt to login, I will always be immediately redirected to the login page again. Something is up with the sessions. It’s been a long time since I used PHP, as far as I remember the sessions are stored in memory or a file.

Anyone know where this session file is saved if it is a file?

Any advice on how multi instance WordPress works with php sessions? I tried using the redis-object-cache plugin but for some reason it still has the same issue? Are there any articles anyone knows of to pull this off?

Please do not mention multi-site, I am not using it. Multi instance means I horizontally scaled one single WordPress site. When I try and search the web for anything, I can only ever find info on multi-sites which is totally getting in the way of Google being useful. I have even tried filtering out search results and I still get endless results about multi-site.

First of all: thank you for all the work you put in with this plugin. I use it on several websites and it works great!

Recently, one of the websites has started showing the notice that the 301 redirect via .htaccess had failed the test.

Here’s my debug info:

General
Plugin version: 3.3.5
SSL certificate is valid
SSL is enabled

Options
* Mixed content fixer
* WordPress redirect
* htaccess redirect

Server information
Server: apache
SSL Type: LOADBALANCER

Detecting configuration

SSL Configuration
testing htaccess rules...
test page url, enter in browser to check manually: /wp-content/plugins/really-simple-ssl/testssl/loadbalancer/ssl-test-page.html
htaccess rules test failed with error: Too many redirects
checking if .htaccess can or should be edited...
.htaccess does not contain default Really Simple SSL redirect
retrieving redirect rules
converting siteurl and homeurl to https
Mixed content fixer successfully detected

Constants
No constants defined

If I go to ssl-test-page.html, it doesn’t open – I get a ERR_TOO_MANY_REDIRECTS error.

My SSL test page shows:

#SSL TEST PAGE#
This page is used purely to test for SSL availability.

#SERVER-HTTPS-ON# (on)
#SERVERPORT443#
#LOADBALANCER#

#SUCCESSFULLY DETECTED SSL#

I have tried to manually edit .htaccess using the guidance you provide at this page, but with no luck. In particular, if I enter the rules listed for #LOADBALANCER#, I lose access to the website and I have to delete the rules to get it working again.

Could anyone help diagnose this? Would it be a server configuration issue to bring up with the hosting provider?

I’d really like to use the .htaccess redirect rather than the WP one, so any help would be much appreciated. Thank you in advance

I have a HA complex setup, where each WP website is replicated on like 10x servers. This includes the database too, and the traffic is load balanced. Also using CF for some benefits.

I tried to use W3 cache but failed because:

1. I cannot use disk cache, because I ignore “cache” folders in replication
2. I cannot upgrade to “enterprise” to use Amazon SNS and APCu cache
3. I do not want to use a CDN to host all the media and such on it

Looking at the code on GitHub, I can see possibility for memcached to work in such environment ?

I was thinking of installing memcached or redis on each server, and then add all the servers in the cache settings – would something like that work ?

Theoretically it should save the cache per website/host on each server ?

I’m not sure if this was ever tested, and I am in production so I cannot really play around too much…

Many thanks for your advice.

In my case im using a load balancer on the site with settings saved in a repo. So why does it sometimes fail to authenticate? This isnt a rackspace issue because the same set up works fine on stage with 1 server.

Side question, which file is the correct settings file now? I see a master.json file but also the master.php and master-admin.php file. Why are there so many settings files and which one do i actually need to use/keep in my repo?

How do I remove the warning:

Because your site is behind a loadbalancer and is_ssl() returns false, you should add the following line of code to your wp-config.php. Your wp-config.php could not be written automatically.

if (isset($_SERVER[“HTTP_X_FORWARDED_PROTO”] ) && “https” == $_SERVER[“HTTP_X_FORWARDED_PROTO”] ) {
$_SERVER[“HTTPS”] = “on”;
}

I’ve already added this to my wp-config and the site is functioning fine.

https://www.ads-software.com/plugins/really-simple-ssl/

i am running a wp blog v 3.0.4 via loadbalancer. the blog is in the subfolger /blog. my problem is, that if you visit the blog through https://www.proxyserver.com/blog it still comes up as https://www.wp-server.com/blog/ . if you enter it with https://www.proxyserver.com/blog/, the right address shows up. i already had a look on various tutorials about that topic but nothing worked out so far. any ideas?

We have a very redundant environment with multiple load-balancers and firewalls, etc.

We have a back-end repository where files are stored in a big array and the front-end webservers rsync content from this back-end repository overwriting any changes made locally on the webservers.

The database is replicated using the mysql replication to another server as well, but until a failure happens, the front-end webservers know only of the primary database server. Regardless…

I noticed the upload option: Options–>Misc in the admin interface which defaults to “wp-content/uploads”.

I am able to “write” to the back-end repository server using an internal IP, etc. and can setup a host called something like “admin.domain.com” and have it resolve to the internal repository IP to post images and uploads to so that it will replicate to all the web servers, but WP will redirect back to the main WordPress address (URL) as defined in the Options area when I try and use a hostname (non-www.domain.com).

For example, the main website is: www.domain.com. My “admin” area, I want to setup is admin.domain.com (which resolves to an internal IP pointing to the repository)

When I do it this way, it just redirects back to the main www.domain.com area.

So my question is:

Q: How do I do this so that just I (we) can update the blog with images/attachments to a host that is not defined in the primary options area.

(Other than just creating an “image.domain.com” host and hard-linking by the way)

Any help is appreciated.

Thanks!