As of this post, WordPress is installed via the ubiquitous docker container on a virtual machine behind the office router.
WordPress is intended to create content for the internet. The problem arises with the other ubiquitous docker container, NGINX Reverse Proxy used in combination to expose the WP server to the internet. The combination is more than a conundrum. Its a trainwreck of some configration in a file somewhere that nobody can answer for.
No matter where one looks on the internet, its seems that operating WordPress out of the box behind the reverse proxy just won’t work. To that end, I will post the fix here in this thread should I find the answer.
In the mean time, operating local will have to suffice.
