Solved Reach Wordpress Site, But Admin Doesn't not loads

[austinsonger]

Main Site

Admin Site

bolded text

I would like to fix this so I can update my website.
I restarted the app, but did not fix it.

[marcusquinn]

Have you tried without specifying the port?

[austinsonger]

Yes....

It actually times out and then shows the port, I would never setup my wordpress, with the port being displayed.

The system is basically doing it by itself.

[girish]

@austinsonger https://domain.com/wp-admin/ loads for me. The trailing slash is important! I guess you got hit by this bug - https://git.cloudron.io/cloudron/wordpress-app/-/issues/40

[marcusquinn]

Interesting read on this subject:

• https://www.danielmorell.com/guides/htaccess-seo/redirects/https-www-and-trailing-slash

Be good to have this as standard in all installs!

[austinsonger]

I was doing that. But I did a server reboot and it started working afterwords.

[marcusquinn]

• https://www.danielmorell.com/guides/htaccess-seo/sample-code/redirect-sample-code

tl;dr

.htaccess for www.

(www maybe better when needing to use a CNAME to point to a load balancer domain, this approach is used by Google.com, Odoo.com enterprise etc)

#### Force HTTPS
#### Force WWW
#### Remove trailing / from file

# Turn on Rewrite Engine
RewriteEngine On

# Remove trailing slash from non-filepath urls
RewriteCond %{REQUEST_URI} /(.+)/$
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^ https://www.example.com/%1 [R=301,L]

# Include trailing slash on directory 
RewriteCond %{REQUEST_URI} !(.+)/$
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^(.+)$ https://www.example.com/$1/ [R=301,L]

# Force HTTPS and WWW 
RewriteCond %{HTTP_HOST} !^www\.(.*)$ [OR,NC]
RewriteCond %{https} off  
RewriteRule ^(.*)$ https://www.example.com/$1 [R=301,L]

.htaccess for root domain

(my preferred, simpler but could be more restrictive for enterprise scaling)

#### Force HTTPS
#### Remove WWW
#### Remove trailing / from file

# Turn on Rewrite Engine
RewriteEngine On

# Remove trailing slash from non-filepath urls
RewriteCond %{REQUEST_URI} /(.+)/$
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^ https://example.com/%1 [R=301,L]

# Include trailing slash on directory 
RewriteCond %{REQUEST_URI} !(.+)/$
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^(.+)$ https://example.com/$1/ [R=301,L]

# Force HTTPS and remove WWW
RewriteCond %{HTTP_HOST} ^www\.(.*)$ [OR,NC]
RewriteCond %{https} off  
RewriteRule ^(.*)$ https://example.com/$1 [R=301,L]

[d19dotca]

@girish I was actually going to post this before too... that trailing slash is important. However, this behaviour only seems to impact the managed app. The unmanaged app doesn't require that trailing slash. Any ideas why these are different?