I install WordPress on my subdirectory with Nginx and proxy pass.
But after clicking on Add plugins or add themes, it shows An unexpected error occurred. Something may be wrong with www.ads-software.com or this server’s configuration. If you continue to have problems, please try the support forums.
https://ibb.co/WtJmSMW
how can I fix this?
Regards
]]>foo.example.com
bar.example.com
our server (and the root location of WordPress) is located at blogs.example.com
These work fine. But when we try and pass a directory on the end of the URL (with, or without a subdomain):
anotherexample.com/blog
foo.bar.com/blogs
These just redirect back to blogs.example.com
We have the CNAME (in domain mapping) set to blogs.example.com
And on the server for our websites we have in our conf file:
ProxyPreserveHost On
ProxyPass / https://blogs.example.com/
ProxyPassReverse / https://blogs.example.com/
We have a DNS for anotherexample.com/blog pointing at this conf file. But we can’t get it to work, the fact that we’re trying to point to a URL with a directory at the end is causing WordPress just to redirect to blogs.example.com.
Any suggestions?
https://www.ads-software.com/extend/plugins/wordpress-mu-domain-mapping/
]]>ProxyPass / https://192.168.13.12/wpdom/
ProxyPassReverse / https://192.168.13.11/wpdom/
And on 192.168.13.11, under docroot, wordpress is installed under directory wpdom/site
For going https://wpdom.com/site everything is fine, but when saving some settings under wp-admin, I end up to url like https://wpdom.fi/wpdom/site/wp-admin/options-general.php?settings-updated=true
Sure, this does not work, as it should be https://wpdom.fi/site/wp-admin/options-general.php?settings-updated=true
Any hints? I have Polylang plugin installed.
]]>We have a apache redirect set up like so:
ProxyPass spoons.website.com https://blogs.example.com/spoons/
ProxyPassReverse spoons.website.com https://blogs.example.com/spoons/
When using permalinks we get 404 when going to spoons.website.com/2012/03/12/hello-world/
When viewing the apache log file we see that wordpress is trying to get spoons.website.com/spoons/2012/03/12/hello-world/ giving us a 404.
Is there a way to get wordpress to work with ProxyPassReverse?
]]>I’ve installed WordPress on a server under /my_blog/ it is configured to work as https://www.mysite.com/blog1/
Now, www.mysite.com points to a different server. This has Apache with mod_proxy and I’ve added the following line to httpd.conf
ProxyPass /blog1 https://192.168.100.60/my_blog
But whenever I hit https://www.mysite.com/blog1/ I get the “Nothing found for My_blog” error. Do I need to hack something in order to get this working?
Contents of .htaccess on the 192.168.100.60/my_blog/
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /my_blog/
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /my_blog/index.php [L]
</IfModule>
# END WordPress
]]>I installed wordpress on opensuse, running apache2 – no problems.
I saw it when i hit www.mydomain.com/wordpress.
I wish to just hit www.mydomain.com (without /wordpress). So i use ProxyPass mod for apache2:
ProxyPass / www.mydomain.com/wordpress
…inside my virtual host directive.
When i hit www.mydomain.com, it just hangs – never loads, and i see (in the access logs of apache2):
GET /wordpress/error/HTTP_BAD_GATEWAY.html.var HTTP/1.1″ 404 1041
Its as if once i forward via the proxy – that wordpress is trying to retrieve from a non-relative URL (or something?).
Can wordpress be used with a proxy pass in this way? Or is it forever stuck in “/wordpress”? What does wordpress do when it returns content / queries files / db’s, etc? What are the URLS?
Please, please – any help, appreciated!
Regards, Sam
]]>Regular access at https://wp.mysite.com/ does a ProxyPass through to wp.mysite.com:8998, and our blog homepage shows up just fine. The URL displayed in the address bar does not show :8998.
However, as soon as you click any link on that page, the URL shown in the address bar picks the :8998 back up and displays it. It shouldn’t / we don’t want it to.
Ideas?
]]>