Tag Info

Hot answers tagged

2

As you said, your siteurl and home in your WP options are wrong. You just need to fix them. Since you put CloudFlare in front of your site and enabled the HTTPS option, your URL actually begins with https:. But the WordPress URL has http:. Change them to https:.


2

It isn't the user nginx is running as that is important, but it is the user php-fpm is running as. After all, it is PHP-FPM that executes the PHP scripts, and WordPress is running under privileges that the PHP-FPM running user has. So, check that your upload directory can be written by the user running PHP-FPM.


1

So apparently, the issue was caused by (and this is as reported by my host) some "code" in some plugins that are not compatible with php+APC cache... Don't know if that's really true, but when we changed the handler back to suPHP, the issue resolved! So for (future) people on wordpress + VPS, keep this in mind. If you are going to install some kinda opcode ...


1

You should download & install - Command line interface for WordPress | WP-CLI [alexus@j ~/alexus.org/wordpress]$ wp --version WP-CLI 0.18.0 [alexus@j ~/alexus.org/wordpress]$ wp core verify-checksums Success: WordPress install verifies against checksums. [alexus@j ~/alexus.org/wordpress]$


1

I recently put all together with Quercus (a PHP5 java implementation) building up a single WAR file with the latest wordpress. http://bonfab.io/?p=85


1

Finally I ignore https and change define( 'FORCE_SSL_ADMIN', true ); in .openshift/config to false, then set http for both siteurl and home.


1

It's most likely the firewall causing the problems. Open up port 9090 with this: sudo iptables -A INPUT -p tcp --dport 9090 -j ACCEPT If you're using ufw: sudo ufw allow 9090 If you would like to redirect all request on port 80 to 9090: sudo iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 80 -j REDIRECT --to-port 9090


1

Ok I found the error. Its i forgot to add those lines to the wp-config.php define('FORCE_SSL_ADMIN', true); if ($_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') $_SERVER['HTTPS']='on';


1

wp-admin is a separate page from index.php so your location directive will never access it. You basically set your location as /WordPress and nest your .php location within it. I'm on a tablet so will add an example code fragment when I get on a desktop/laptop again.


1

Easiest way would be to add: Redirect permanent /forum http://otherserver to your apache vhost config, or to add: RewriteRule ^/forum(.*)$ http://otherserver/$1 [R=301,NC,L] to your .htaccess.


1

would this scenario even be considered a DMZ? Yes. When exposing an internal service to the external world it's always a best practice to secure your others internal services by putting this public service in a DMZ. Basically, this DMZ will be a new network segment routed by a dedicated firewall interface. In case of a single firewall, you will need ...


1

I downloaded the theme again from the developer, and I uploaded the theme files to my server, not overwriting existing files, and it fixed it. How my files vanished is truly a mystery.



Only top voted, non community-wiki answers of a minimum length are eligible