404 Error on The Things Stack Console on Ubuntu Server in Proxmox

1

I’m facing an issue while running The Things Stack in my environment. Here’s what has been done and configured so far:

  • Environment:

    • Virtual Ubuntu Server hosted on Proxmox.

    • Public IP configured and the domain pointing correctly to this IP. The domain resolves without issues.

    • All necessary ports for the Network Server are open, according to the official documentation (HTTP, HTTPS, MQTT, MQTT-TLS, gRPC, UDP for LoRaWAN, etc.).

  • Docker Configuration:

    • The docker-compose.yml is set up correctly with PostgreSQL, Redis, and the Stack container.

    • Environment variables and volume paths are correctly configured, including directories for blobs and configuration files.

    • All required keys for cookies, cluster, gateway token, etc. have been generated and are functional.

  • The Things Stack Configuration (ttn-lw-stack-docker.yml):

    • The domain tts.XXX.puc-rio.br is configured in all relevant sections: Console, Identity Server, Network Server, Application Server, and Join Server.

    • TLS configuration: initially using Let’s Encrypt (ACME), with the directory /var/lib/acme correctly mounted in Docker.

    • Alternatives for TLS considered: disabled (source: none) for testing, or using custom certificates.

  • Observed Issue:

    • When starting the stack, all services initialize correctly and the logs show no critical errors (Redis, PostgreSQL, Identity Server, Network Server, Application Server, Join Server, Console, Gateway Configuration Server).

    • However, when accessing the Console via browser, registering a user and logging in results in a 404 - Page Not Found.

    • Attempts to adjust TLS (ACME or custom certificates) did not solve the issue.

  • Additional Details:

    • gRPC attempts to start with TLS, but fails if certificates are missing (open cert.pem: no such file or directory).

    • Testing with TLS disabled allows the stack to start, but the Console still returns a 404 error.

    • Docker Compose shows no critical errors and the containers remain running.

Question for the community:
Has anyone experienced a similar situation where the The Things Stack Console returns a 404 even with domain, ports, and TLS configured correctly? What would be the next steps to diagnose or fix this issue?

Thank you in advance

2

Hey everyone, good afternoon! It was my mistake; I missed the last step. I managed to deploy the platform.

3

It would help if you said exactly which last step so it’s clear to anyone finding this thread via Google.