Closed LeviSnoot closed 1 year ago
I don't understand where /v1/instance
is coming from. It looks like an error from the nextjs proxy, but it should never be trying to forward requests to a URL that looks like that, and if it did, it should be able to talk to :8080
since it's running in the same container.
Check the container logs for micro, the API might be crashing at startup and the container isn't restarting because it's kinda terrible. That still doesn't explain the path its trying to access though..
If that doesn't help, joining the discord server and pinging me will be faster.
Closing as I went for rootless docker instead and that seems to work.
I'm running micro through podman. When I deploy it, I get the expected invite URL in the logs, but with a double slash after the domain:
But trying to visit either
https://url.example.com//invite/bunchoflettersandnumbers
orhttps://url.example.com/invite/bunchoflettersandnumbers
results in the following log message:and the website itself gives a 500 error.
I'm reverse proxying micro with Nginx. Here's the vhost file:
My
.microrc.yaml
My
docker-compose.yml
:I've tried allowing port 8080 through my firewall (ipv4 and ipv6) just in case, but that didn't solve it. My guess is something is using port 8080 that shouldn't be, but I'm not sure if that's on the host system or one of the containers.