Problem with Ratel

[vladimir]

I need to report a problem. I am using the following compose.yml file:

version: "3.8"
services:
  zero:
    image: dgraph/dgraph:v23.0.0
    container_name: dgraph_zero_one
    volumes:
      - ./tmp/data:/dgraph
    ports:
      - 5080:5080
      - 6080:6080
    restart: on-failure
    command: dgraph zero --my=zero:5080
  alpha:
    image: dgraph/dgraph:v23.0.0
    container_name: dgraph_alpha_one
    volumes:
      - ./tmp/data:/dgraph
    ports:
      - 8080:8080
      - 9080:9080
    restart: on-failure
    command: dgraph alpha --cache size-mb=2048 --my=alpha:7080 --zero=zero:5080 --security whitelist=0.0.0.0/0
  ratel:
    image: dgraph/ratel:v21.12.0
    container_name: ratel
    ports:
      - 8000:8000
    restart: on-failure
    command: dgraph-ratel

When I go to localhost:8000 I get the following error

When I use the address https://localhost:8000, it redirects me to https://localhost:8000/login

If this is a new splash screen, then what are the login and password?
If this is a new form of fraud, then how can you fight it?

[matthewmcneely]

Check your docker logs for Ratel. I believe there is something else on your machine binding port 8000.

[MichelDiz]

Hmm, it seems like this isn’t related to Docker or Ratel at all. Maybe your organization has set up a redirect through a reverse proxy. However, it’s strange that it is redirecting the localhost.

It’s definitely something like this because Ratel doesn’t have TLS capabilities on its own and it doesn’t perform any redirects. It simply cannot do that.

And we are not connected to “Incredibuild” in any way.

It seems like your browser has a valid certificate for localhost. Strange, how did you manage to do that? In theory, you can’t issue certificates for addresses that you don’t own. You can issue certificates as if you were a certificate authority, but they won’t be considered 100% valid.

There is definitely something wrong with your machine or local network.