Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docker version stop responding after every Brave browser update on Windows client. Error 500. #24

Open
baiomys opened this issue Jul 21, 2024 · 4 comments

Comments

@baiomys
Copy link

baiomys commented Jul 21, 2024

Docker service is hosted on separate LAN server, MAC_VLAN network.
All other services hosted on same service IP (same docker-compose) also stop working until complete restart (via docker-compose down/up), which is very disappointing behavior.

incus:
    image: 'penninglabs/lxconsole:latest'
    restart: always
    volumes:
      - ./incus/certs:/opt/lxconsole/certs
      - ./incus/server:/opt/lxconsole/instance
    networks:
      vlan110:
        ipv4_address: 10.100.100.100
    dns:
      - 1.1.1.1

networks:
  vlan110:
    driver: macvlan
    driver_opts:
      parent: int_gst
    ipam:
      config:
        - subnet: "10.100.100.0/24"
          gateway: "10.100.100.2"
@matthewalanpenning
Copy link
Contributor

Do you know if there are any error logs either from the docker container itself or from the Brave browser that would indicate what the failure is?

@baiomys
Copy link
Author

baiomys commented Jul 23, 2024

Take a look.
error.txt

@matthewalanpenning
Copy link
Contributor

Version 0.5.7 was just released to fix this issue. So it appears as though when the Brave browser is updating it is removing all Session state values in the browser. I did find a few bug reports on this already:

I added a conditional check for the session value that was erroring out and now log the user out when this happens. This should prevent you from having to restart LXConsole when this happens.

Thanks for finding this issue.

@baiomys
Copy link
Author

baiomys commented Jul 29, 2024

Glad to hear about nasty bug fix.
Thanks for quick response.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants