The route api/auth/register could not be found.

[mike-dataduality]

I'm trying to setup a production instance of Hi.events over multiple docker containers, but I just can't get the app to work. I keep getting The route "api/auth/register could not be found." when trying to register a new user, and going to the api link gives me a 404.

I have containers for the frontend, backend, postgres, redis, nginx and certbot-renawal.

backend compose config files:

services:
  hi-events-backend:
    build:
      context: ./../../backend
      dockerfile: Dockerfile
    container_name: hi-events-backend
    ports:
      - "8124:80"
    networks:
      - hi.events
    environment:
      APP_KEY: "base64:secret="
      APP_SAAS_MODE_ENABLED: "true"
      APP_FRONTEND_URL: "https://tickets.mihow.net"
      APP_CDN_URL: "https://tickets.mihow.net/storage"
      FILESYSTEM_DISK: "s3-public"
      JWT_SECRET: "secret"
      LOG_CHANNEL: "stderr"
      AWS_ACCESS_KEY_ID: "secret"
      AWS_SECRET_ACCESS_KEY: "secret"
      AWS_DEFAULT_REGION: "ap-melbourne-1"
      AWS_PUBLIC_BUCKET: "bucket-hi.events"
      AWS_PRIVATE_BUCKET: "bucket-hi.events"
      STRIPE_PUBLIC_KEY: "secret
      STRIPE_SECRET_KEY: "secret"
      MAIL_MAILER: "smtp"
      MAIL_HOST: "email-smtp.ap-southeast-2.amazonaws.com"
      MAIL_PORT: "2587"
      MAIL_USERNAME: "AKIAWD2CYLD7ZV3IZ362"
      MAIL_PASSWORD: "secret"
      DB_CONNECTION: "pgsql"
      DB_HOST: "localhost"
      DB_PORT: "5432"
      DB_DATABASE: "hi.events"
      DB_USERNAME: "postgres"
      DB_PASSWORD: "secret"
      REDIS_HOST: "localhost"
      REDIS_PASSWORD: "secret"
      REDIS_USER: "default"
      REDIS_PORT: "6379"
      REDIS_URL: ""
      QUEUE_CONNECTION: "redis"
      DATABASE_URL: ""
      STRIPE_WEBHOOK_SECRET: "secret"
  
networks:
  hi.events:
    external: true

front end compose file

services:
  hi-events-frontend:
    build:
      context: ./../../frontend
      dockerfile: Dockerfile.ssr
    container_name: hi-events-frontend
    ports:
      - "8125:80"
    networks:
      - hi.events
    environment:
      VITE_STRIPE_PUBLISHABLE_KEY: "pk_test_51RDIyYRtFNb5Q6HveFkihkW1I9txoGBQlDsZuJNMJIHzuHkne4Y9UUhjtQSCio6FmvGqa4KS3EqzQWQYuBuL3jkW009ersr34l"
      VITE_API_URL_SERVER: "https://hi-events-backend:8080/api"
      VITE_API_URL_CLIENT: "https://tickets.mihow.net/api" 
      VITE_FRONTEND_URL: "https://tickets.mihow.net"
networks:
  hi.events:
    external: true

my config for nginx:

server {
    listen 80;
    server_name tickets.mihow.net;

    # Handle ACME challenge for Certbot validation
    location /.well-known/acme-challenge/ {
        root /var/www/html;
    }

    # Redirect all HTTP traffic to HTTPS
    location / {
        return 301 https://$host$request_uri;
    }
}

server {
    listen 443 ssl http2;
    server_name tickets.mihow.net;

    # SSL Certificates
    ssl_certificate /etc/letsencrypt/live/tickets.mihow.net/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/tickets.mihow.net/privkey.pem;

    # SSL Configuration (Optional for stronger security)
    ssl_protocols TLSv1.2 TLSv1.3;
    ssl_ciphers 'ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256';
    ssl_prefer_server_ciphers on;

    # Route API calls to backend
    location /api/ {
        proxy_pass http://hi-events-backend:8080; #8080
        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;
    }

    # Handle the main proxying to the frontend app
    location / {
        proxy_pass http://hi-events-frontend:5678;  #5678  Forward requests to the frontend app
        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 Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
    }
}

ChatGPT is not that great in resolving this issues, it keeps looping with the same troubleshooting approach

[daveearley]

I'd recommend splitting your backend and frontend into separate domains instead of using /api under the same domain. For example:

• api.tickets.mihow.net → backend
• tickets.mihow.net → frontend

This will make your NGINX config simpler. Your setup would look something like this:

VITE_API_URL_CLIENT=https://api.tickets.mihow.net
VITE_API_URL_SERVER=https://api.tickets.mihow.net

Here’s a basic (untested) example NGINX config for the backend:

server {
    listen 443 ssl;
    server_name api.tickets.mihow.net;

    ssl_certificate /etc/letsencrypt/live/api.tickets.mihow.net/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/api.tickets.mihow.net/privkey.pem;

    location / {
        proxy_pass http://hi-events-backend:80;
        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;
    }
}

[mike-dataduality]

Well I made progress by setting up the second sub-domain as suggested, but I completely scrapped and redid my reverse proxy setup using NGINX and ACME companion.

Now I can get to the API url no issues, but I am facing other issues which I'll raise a different bug for as it seems the DB objects are not being setup properly.