404 errors when using CMD_URL_PATH in new 2.6.0 #1936

Activity

1. Yukaii

   modified the milestone: 2.6.1 on Aug 13, 2025
2. Yukaii

   linked a pull request that will close this issueFix: 404 errors for static assets when using CMD_URL_PATH configuration #1943on Sep 18, 2025
3. Yukaii commented on Sep 30, 2025

   

   Yukaii

   on Sep 30, 2025

   Member

   More actions

   You should probably use a reverse proxy like nginx or Caddy to host your CodiMD application. Below is an example config:

   ---

   server {
       listen 80;
       server_name yourdomain.com;
   
       # Redirect root to /codimd/
       location = / {
           return 301 /codimd/;
       }
   
       # Redirect /codimd to /codimd/
       location = /codimd {
           return 301 /codimd/;
       }
   
       # Handle /codimd/* requests
       location /codimd/ {
           # Strip /codimd prefix before forwarding
           rewrite ^/codimd/(.*)$ /$1 break;
           
           proxy_pass http://codimd:3000;  # Your CodiMD container
           proxy_set_header Host $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 X-Forwarded-Prefix /codimd;
           
           # WebSocket support
           proxy_http_version 1.1;
           proxy_set_header Upgrade $http_upgrade;
           proxy_set_header Connection $connection_upgrade;
       }
   }
   
   # WebSocket upgrade map
   map $http_upgrade $connection_upgrade {
       default upgrade;
       '' close;
   }

   👍React with 👍1Reacted by AriesyuGTH