To address the issue where some request URLs are missing the /apollo prefix after adding it to the access path in Apollo Portal, causing configuration imports to fail, follow these steps:

1. For Apollo Portal version 1.7.0 and above:

   • Ensure you've added the -D parameter server.servlet.context-path=/apollo or the system environment variable SERVER_SERVLET_CONTEXT_PATH=/apollo for apollo-portal.
   • Update your nginx/slb configuration to forward requests correctly. Here's an nginx configuration example:

     location /apollo/ {
         proxy_set_header X-Forwarded-Host $host;
         proxy_set_header X-Forwarded-Server $host;
         proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
         proxy_pass http://127.0.0.1:8070/apollo/;
     }

2. For Apollo Portal version 1.6.0 and above:

   • Add the prefix.path=/apollo configuration parameter to the portal through the Administrator Tools - System Parameters page.
   • Use the following nginx configuration for forwarding:

     location /apollo/ {
         proxy_set_header X-Forwarded-Host $host;
         proxy_set_header X-Forwarded-Server $host;
         proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
         proxy_pass http://127.0.0.1:8070/;
     }

These steps ensure that the /apollo prefix is correctly handled, allowing for successful configuration imports. If the issue persists, please provide the exact error message and any relevant logs for further assistance. Ensure you have correctly added the /apollo prefix as per the recommended approach using server.servlet.context-path.

To continue the conversation, mention @dosu.

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in 7 days unless it is tagged "help wanted" or other activity occurs. Thank you for your contributions.