Wordpress image

[vicmosin]

I installed an official WP docker container. Container running in front of nginx instance.

Here is the .htaccess file that I inject to container:

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]

# add a trailing slash to /wp-admin
RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]

RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) $2 [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
RewriteRule . index.php [L]
</IfModule>

Nginx just proxies /wp to appropriate path. The problem is the following: https://example.com/wp/ and https://example.com/wp/hello-post/ work fine. But once I try to get an access to https://example.com/wp/wp-admin/ it redirects me all the time to https://example.com/wp-admin/ i.e. ignores wp subfolder.. I tried to use .htaccess which comes by default - exactly same story.

The full description is here

[Douglasdc3]

This issue could be due to the configuration of the apache2.conf

<Directory /var/www/>
	Options Indexes FollowSymLinks
	AllowOverride None
	Require all granted
</Directory>

Apache2 will actually not read the .htaccess file at all.

Could be related to #158 (is closed but with the latest worpress image the issue does not seem to be fixed)

[yosifkit]

That is in the apache2.conf, but that should be overridden by the other config file:

$ cat /etc/apache2/conf-enabled/docker-php.conf 
<FilesMatch \.php$>
	SetHandler application/x-httpd-php
</FilesMatch>

DirectoryIndex disabled
DirectoryIndex index.php index.html

<Directory /var/www/>
	Options -Indexes
	AllowOverride All
</Directory>

[vicmosin]

.htaccess seems to work indeed.. The interesting thing is that it happens only inside wp-admin area.. i.e. even links on the main page are fine (check out the attachment) But one I click on one of the links it redirects me to wp-admin without subfolder

[tianon]

Were your permalinks setup properly? In my experience, a given WordPress install is very picky about where it was initially installed, and isn't a fan of being moved (see https://codex.wordpress.org/Giving_WordPress_Its_Own_Directory#Method_II_.28With_URL_change.29 for some tips/docs around that).

[vicmosin]

@Douglasdc3 @yosifkit Yeah, I can confirm that cat /etc/apache2/conf-enabled/docker-php.conf gives me

<Directory /var/www/>
	Options -Indexes
	AllowOverride All
</Directory>

so values in apache2.conf should be indeed overriden.
But sill have the issue.. Any other ideas?

[tianon]

Sorry for the delay.

Do you have a simple way to reproduce the issue? I haven't seen any issues in the usage of this container with .htaccess or permalinks in my now several years of usage, so having a way to reproduce this issue would be really helpful to figuring out what's going on in your environment.

You'll probably also have more luck getting timely responses from the Docker Community Forums, the Docker Community Slack, or Stack Overflow (since this is an issue tracker, not a support forum, and we typically have a high volume of filed issues to try to keep up with).

[tianon]

Closing since there doesn't seem to be anything actionable we can fix here -- as noted above, please try the forums, etc if there's additional information available which could help other folks debug (or at least reproduce) the issue.