Hard coded /admin/init not using the proxy settings in the server config

[derrickmehaffy]

Bug report

Describe the bug

There is a hard coded /admin/init path that doesn't use the proxy settings leading to a failure to connect under certain types of proxying.

strapi/packages/strapi-admin/admin/src/containers/App/index.js

Lines 57 to 60 in 4add565

	try {
	const { data } = await request('/admin/init', { method: 'GET' });
	const { uuid } = data;

Steps to reproduce the behavior

Attempt to set a proxying config where Strapi doesn't serve the Admin panel is instead the proxy application tries to serve it from the Strapi root such as:

server {

# Listen HTTP
    listen 80;
    server_name strapi.guru;

# Static Root
    location / {
        root /var/www/html;
    }

# Client 1
   location /client-01/api/ {
        rewrite ^/client-01/api/(.*)$ /$1 break;
        proxy_pass http://client1;
        proxy_http_version 1.1;
        proxy_set_header X-Forwarded-Host $host;
        proxy_set_header X-Forwarded-Server $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header Host $http_host;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "Upgrade";
        proxy_pass_request_headers on;
    }

# This right here is a symlink of the build folder into the /var/www/html folder, assuming the request should be to
# http://strapi.guru/client-01/init and not http://strapi.guru/client-01/admin/init
    location /client-01/ {
        root /var/www/html;
    }
}

See the following server.js file for example:

module.exports = ({ env }) => ({
  host: env('HOST', '0.0.0.0'),
  port: env.int('PORT', 1337),
  url: env('NGINX_URL', 'http://strapi.guru/client-01'),
  admin: {
    serveAdminPanel: false,
    auth: {
      secret: env('ADMIN_JWT_SECRET'),
    },
  },
});

Expected behavior

Admin should be using the proxy settings and adjusting this request

Screenshots

System

• Node.js version: v14
• NPM version: v6
• Strapi version: 3.2.1
• Database: PostgreSQL
• Operating system: Ubuntu 18.04

[derrickmehaffy]

Attempts at forcing the rewrite from the proxy side also fail as Strapi sees it as /init instead of /admin/init and attempts at forcefully overriding the above file from the */App/index.js lead it to lose all the information about the proxy completely.

    location /client-01/ {
        rewrite ^/client-01/admin/(.*)$ /client-01/$1 break;
        root /var/www/html;
    }

[derrickmehaffy]

This issue has been mentioned on Strapi Community. There might be relevant details there:

https://forum.strapi.io/t/can-strapi-run-in-a-reverse-proxied-container-using-nginx/156/16

[kneczaj]

I confirm. In server.js it is enough to set url like this:

url: '/api',

and the error occurs.

This places admin at /api/admin and it loads, and then stops at a reaquest to init

[derrickmehaffy]

url: '/api',

Generally we do have issues if you are using a relative URI for the root url key and should use a direct one if possible. But yes even in these cases the /admin/init is still hard coded.

[derrickmehaffy]

This issue has been mentioned on Strapi Community. There might be relevant details there:

https://forum.strapi.io/t/email-validation-account-link-wrong-base-url/1300/5

[kneczaj]

url: '/api',

Generally we do have issues if you are using a relative URI for the root url key and should use a direct one if possible. But yes even in these cases the /admin/init is still hard coded.

My use case is to put strapi at /api at the gateway so I can redirect all the others urls to frontend. Having one gateway for frontend and backend with the backend at a relative url has a big advantage. You do not need to store backend url in any environment variable for frontend code. This is very useful when using multiple environments e.g. test/prod/pull request deployments. Especially at pull request deployments where gateway url is random this makes a lot of sense.