Client Portal: [POST] "https://directus.mydomain.xyz/auth/login": <no response> NetworkError when attempting to fetch resource.

[den5o]

Self hosted instance of directus and agency-os. Running in podman containers in 2 separate VMs. Agency-os built successfully without any customisation, and deployed using the latest node image.

Frontend and portal login page load normally. This is the error when the login button is pressed:

Trying to access https://directus.mydomain.xyz/auth/login results in:

Node container shows no logs other than: Listening on http://[::]:3000

[bryantgillespie]

It looks like the AgencyOS frontend is not able to find the Directus backend. I'm not a Podman user but I'd take a look at your networking settings.

[den5o]

I triple checked this before opening the issue.

This is from inside the node container:

[apps@frontend ~]$ podman exec -it agencyos_node_1 /bin/sh
# curl https://directus.mydomain.xyz
Found. Redirecting to ./admin  
# curl https://directus.mydomain.xyz/auth/login
{"errors":[{"message":"Route /auth/login doesn't exist.","extensions":{"path":"/auth/login","code":"ROUTE_NOT_FOUND"}}]}

This is the log entry of the directus container every time the sign in button is pressed: OPTIONS /auth/login 200 20ms

[Bollznet]

Hi had the same problem and I'm in localhost.

[den5o]

I'm revisiting this and have tried the following:

I built the frontend on the host running the directus container twice with different .env files.

In the first instance I served it again using a podman node container attached to the same pod as directus using DIRECTUS_URL="http://<directus-container-ip>:<directus-port>".

In the second instance I served it directly on the host exposing it on a different port behind my reverse proxy and used DIRECTUS_URL="https://directus.mydomain.xyz"

In both instances SITE_URL="https://mydomain.xyz" was used with the frontend being accessible through a browser just like my original post.

I then deployed a fresh instance of directus and agencyos locally on my workstation accessing them on localhost and the issue persists.

I all instances running curl http[s]://<directus-domain/ip:port>/auth/login results in {"errors":[{"message":"Route /auth/login doesn't exist.","extensions":{"path":"/auth/login","code":"ROUTE_NOT_FOUND"}}]}