aerokube / selenoid-ui

Graphical user interface for Selenoid project
https://aerokube.com/selenoid-ui/latest/
Apache License 2.0
305 stars 76 forks source link

Error connecting to SSE #446

Closed evalalos closed 2 years ago

evalalos commented 3 years ago

Hi guys, I have a problem with starting selenoid-ui, SSE has an issue. Thanks in advance

Attaching all logs:

Console log: EventSource's response has a MIME type ("application/json") that is not "text/event-stream". Aborting the connection. index.js:101 Error connecting to SSE http://localhost:8888/events

Docker container log: 2021/08/05 13:31:53 [INIT] [Listening on :8080] 2021/08/05 13:31:57 Client added. 1 registered clients 2021/08/05 13:31:57 Client added. 2 registered clients 2021/08/05 13:32:02 Client added. 3 registered clients 2021/08/05 13:32:02 Client added. 4 registered clients 2021/08/05 13:32:03 Removed client. 3 registered clients .....

selenoid

vania-pooh commented 3 years ago

@evalalos do you have Nginx or another reverse proxy behind Selenoid UI?

dvdvdmt commented 2 years ago

Hello @vania-pooh it seems I have very similar problem with SSE. I use this docker-compose.yml:

version: '3'
services:
  selenoid:
    image: "aerokube/selenoid:latest-release"
    network_mode: bridge
    ports:
      - "4444:4444"
    volumes:
      - "/var/run/docker.sock:/var/run/docker.sock"
      - "~/Documents/config/:/etc/selenoid/:ro"
    command: -limit 20 --timeout 3m
  selenoid-ui:
    image: "aerokube/selenoid-ui:latest-release"
    network_mode: bridge
    links:
      - selenoid
    ports:
      - "8042:8080"
    command: ["--selenoid-uri", "http://selenoid:4444"]

After their start I see the errors in the selenoid-ui image Endpoint http://selenoid:4444/status response with an error: {"errors":[{"msg":"can't get status"}],"version":"1.10.4[2021-10-10_08:53:47AM]"}. I'm using the latest Docker for Mac v4.1.1. Could you please give me any advise on what should I check to figure out what is the problem?

dvdvdmt commented 2 years ago

I figured out that the problem disappears on the old Docker Version 4.0.0 (4.0.0.12). But only in case you go to the Preferences > Experimental Features and disable "Use Docker Compose V2 release candidate". image The fresh docker of v4.1.x doesn't have such setting.

dvdvdmt commented 2 years ago

There is also a command that switches Docker Compose V2 back to Python's docker-compose:

docker-compose disable-v2

Here are the details.

kim-andrew-v commented 2 years ago

It helps, thanks @dvdvdmt !