Can only access Para on localhost

I’ve been trying to set up Para on a test server and mapping it with Nginx and a reverse proxy, but neither Scoold nor para-cli can acces it on the public ip. Accessing it through localhost works fine however.

Endpoints like /v1/_setup however work with the public ip. I’ve tried both Nginx and running it directly on an open port.

Config I’m using for Nginx:

server {
       listen 32461 http2;
       listen [::]:32461 http2;

       location / {
        proxy_pass       http://localhost:8080;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header Host $http_host;
       }
}

Logs are not giving me anything informative either, any idea where I can start debugging?

[wleev]

This has been fixed, error on my part due to a mix-up of keys and my dev server lacking outbound access.

Thanks for the support, it helped me narrow down the cause.

[albogdano]

Hm, yea it is kinda strange. The ping URL is GET /v1/_me and para-cli setup just configures the CLI tool to connect to a specific Para server, but it doesn’t call /v1/_setup automatically. That is only needed to initialize the Para server. The CLI config file is located somewhere in your home directory.