Custom domain assigned to Dokploy server gives 404 not found #3067
-
|
So I have assigned dokploy.example.com as the custom domain for my Dokploy server but when I go to the domain it says "404 page not found". However, the same domain works with dokploy.example.com:3000 but even on this I cant login due to invalid origin. I do have "A" record on my domain pointing to the server IP. I already have a couple of next/nest services up and running on dokploy. From a security point of view, I need to assign a custom domain to DokPloy to allow https. Please do help. I have also tried removing the custom domains from all my servcies but that didn't help This same behaviour is noticed on my adminer service where the custom domain assigned gives 404 page not found but the default traefik domain works |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Figured it out, I had another next service running on port 3000 which was causing dokploy domain to not work, I reassigned a different port to that service and now the domain works. For the adminer, I just had to remove the traefik default domain then my custom domain also worked |
Beta Was this translation helpful? Give feedback.
Figured it out, I had another next service running on port 3000 which was causing dokploy domain to not work, I reassigned a different port to that service and now the domain works. For the adminer, I just had to remove the traefik default domain then my custom domain also worked