mkadin
1
We’re using the lastest version of redash and have installed it via the AWS AMI. We’d like to run redash on a different port than 80 and 443 so we can terminate SSL and do some auth upstream of redash as we do with other internal applications. How do you run redash on another port? I can’t seem to find any docs on that.
Starting from redash-5.0.2-b5486-build2-us-east-2 (ami-009571af26dc2a231)
arikfr
2
First, v5.0.2 isn’t the latest version any more. We released the final version of v8 a few days ago and also created new AMIs. I recommend upgrading or just replacing the AMI with the new one, if you don’t have any content on this one.
As for your question:
Redash runs its own server listening on port 5000 and an nginx proxy listening on port 80. There is nothing listening on port 443.
If you want to change any of the ports Redash is listening on, just update the docker-compose.yml file (located in /opt/redash). You can reassign the host port it binds to to whatever makes sense in your case.
Hi arikfr
I am trying to run redash_server docker container with different port (i.e 5050 instead of 5000).
By editing docker-compose.yml file, I did run redash_server container with 5050 port.
But when I run redash client with REDASH_BACKEND=“http://localhost:5050”, I am getting the following error
[HPM] Error occurred while trying to proxy request /api/session from localhost:8083 to http://localhost:5050/ (ECONNRESET)
So, I did check log of redash_server continer, and I found it’s listening still 5000 port even if I did change port in docker-compose.yml file.
#docker ps
#redash_server logs
