Websocket connection fails for 'Instance on localhost' #339
Description
System Info
- Host OS: Linux Mint 21.3 (Virginia)
- Linux Kernel: 6.8.0-65-generic
- Python 3.10.12
- everest-admin-panel version: tag: v0.5.1
- everest-core version: tag: chargebridge-0.1 (also tried with latest main)
Description
I am going through this Quick Start Guide and reached to the admin panel section. I have successfully installed all the dependencies and built the core framework as well as the standalone admin panel.
I am running the run-sil.sh script and interacting with the simulations hosted at http://localhost:1880/ui/ and so far it works well. Then I tried to access to the admin-panel either via http://localhost:8849 for the built-in panel or via http://127.0.0.1:8080 for the standalone version that I'm running. Both can load successfully.
Then I tried to connect to the Instance on localhost as suggested in the quick start guide. So I configure it to use ws://127.0.0.1:9001 but both panels fail to connect to websocket. I get the error message "Connection failed. Trying to reconnect.".
The docker container for mqtt-server logs that it's opening a WebSocket port on port 9001. So I thought maybe the guide is referencing to a wrong port number then I used the port 9001 instead. The websocket connection on my browser succeeded this time but it doesn't go beyond the message "Successfully opened WebSocket connection" and keeps spinning a 'loading' animation.
Logs
I get no errors on any of steps but I will leave all the logs here for reference:
everest-workspace $ docker network create --driver bridge --ipv6 --subnet fd00::/80 infranet_network --attachable
5931dc57531f99bc12ee392ae87f66285178f45007e1fdcc1277da74f2b91cdd
everest-workspace $ docker run --name mqtt-server --network infranet_network -p 1883:1883 -p 9001:9001 ghcr.io/everest/everest-dev-environment/mosquitto:docker-images-v0.1.0
1764239293: mosquitto version 2.0.10 starting
1764239293: Config loaded from /mosquitto/config/mosquitto.conf.
1764239293: Opening ipv4 listen socket on port 1883.
1764239293: Opening ipv6 listen socket on port 1883.
1764239293: Opening websockets listen socket on port 9001.
1764239293: mosquitto version 2.0.10 running
1764239393: New connection from 172.18.0.1:51722 on port 1883.
1764239393: New client connected from 172.18.0.1:51722 as auto-7D8DA85E-8F9C-C34C-592A-25829DFD8389 (p2, c1, k600).
1764239393: New connection from 172.18.0.1:51730 on port 1883.
1764239393: New client connected from 172.18.0.1:51730 as auto-F97372DA-CD89-10AB-2980-BBF31C61418E (p2, c1, k600).
1764239393: New connection from 172.18.0.1:51746 on port 1883.
1764239393: New client connected from 172.18.0.1:51746 as auto-E1C0E698-4DAD-0A51-E44C-72287C0CB9A4 (p2, c1, k600).
1764239393: New connection from 172.18.0.1:51756 on port 1883.
1764239393: New client connected from 172.18.0.1:51756 as auto-7FEEBDC8-0890-2583-02BE-FD175A0E9B01 (p2, c1, k600).
1764239393: New connection from 172.18.0.1:51764 on port 1883.
1764239393: New client connected from 172.18.0.1:51764 as auto-B8DE74AF-7BCA-00D2-BFDD-ED30AF000175 (p2, c1, k600).
1764239393: New connection from 172.18.0.1:51768 on port 1883.
1764239393: New client connected from 172.18.0.1:51768 as auto-5CD17F45-E28E-B050-2AB9-7EF72896F398 (p2, c1, k600).
1764239393: New connection from 172.18.0.1:51778 on port 1883.
1764239393: New client connected from 172.18.0.1:51778 as auto-0B37F3D9-CD24-2C59-A34F-5FF88BE1E49C (p2, c1, k600).
1764239393: New connection from 172.18.0.1:51786 on port 1883.
1764239393: New client connected from 172.18.0.1:51786 as auto-B8BA016B-D84E-0AD2-7F81-02E83EB13096 (p2, c1, k600).
1764239393: New connection from 172.18.0.1:51790 on port 1883.
1764239393: New client connected from 172.18.0.1:51790 as auto-E7425169-BAC7-8866-CEC4-D5925A8E5CFB (p2, c1, k600).
1764239393: New connection from 172.18.0.1:51802 on port 1883.
1764239393: New client connected from 172.18.0.1:51802 as auto-2780A26E-8CDF-56DD-684B-B0E785A2AEEC (p2, c1, k600).
1764239393: New connection from 172.18.0.1:51826 on port 1883.
1764239393: New connection from 172.18.0.1:51816 on port 1883.
1764239393: New connection from 172.18.0.1:51814 on port 1883.
1764239393: New connection from 172.18.0.1:51836 on port 1883.
1764239393: New connection from 172.18.0.1:51848 on port 1883.
1764239393: New client connected from 172.18.0.1:51814 as auto-DEB1536B-0B45-3583-A3F3-4C35C7A11ED2 (p2, c1, k600).
1764239393: New client connected from 172.18.0.1:51826 as auto-B1D9C646-1023-52DA-8527-AAD89F835C45 (p2, c1, k600).
1764239393: New client connected from 172.18.0.1:51836 as auto-74E778F0-F364-7291-AE09-91C6E914FE92 (p2, c1, k600).
1764239393: New client connected from 172.18.0.1:51848 as auto-558B7F80-2FAE-2A5F-8C32-C01B92E70D40 (p2, c1, k600).
1764239393: New client connected from 172.18.0.1:51816 as auto-85FA8DD4-A692-5314-6560-9CE3F4F20830 (p2, c1, k600).
1764239393: New connection from 172.18.0.1:51868 on port 1883.
1764239393: New connection from 172.18.0.1:51852 on port 1883.
1764239393: New client connected from 172.18.0.1:51868 as auto-DE6868FF-4A7F-DC77-205B-524E2E7649F3 (p2, c1, k600).
1764239393: New client connected from 172.18.0.1:51852 as auto-ED5D1D0B-C475-B87A-F84D-D9F21F786517 (p2, c1, k600).
1764239393: New connection from 172.18.0.1:51880 on port 1883.
1764239393: New client connected from 172.18.0.1:51880 as auto-0284417B-1A1C-249D-BC04-8B56123710E1 (p2, c1, k600).
1764239415: New connection from 172.18.0.1:56220 on port 1883.
1764239415: New client connected from 172.18.0.1:56220 as nodered_6461ec675ada67c1 (p2, c1, k60).
everest-workspace $ source ./everest-dev-environment/venv/bin/activate
(venv) everest-workspace $ ./everest-core/build/run-scripts/run-sil.sh
2025-11-27 11:29:53.385059 [INFO] manager :: ________ __ _
2025-11-27 11:29:53.385270 [INFO] manager :: | ____\ \ / / | |
2025-11-27 11:29:53.385283 [INFO] manager :: | |__ \ \ / /__ _ __ ___ ___| |_
2025-11-27 11:29:53.385290 [INFO] manager :: | __| \ \/ / _ \ '__/ _ \/ __| __|
2025-11-27 11:29:53.385297 [INFO] manager :: | |____ \ / __/ | | __/\__ \ |_
2025-11-27 11:29:53.385302 [INFO] manager :: |______| \/ \___|_| \___||___/\__|
2025-11-27 11:29:53.385309 [INFO] manager ::
2025-11-27 11:29:53.385314 [INFO] manager :: everest-framework 0.23.1 @v0.23.1
2025-11-27 11:29:53.385319 [INFO] manager :: everest-core 2025.9.0 @chargebridge-0.1
2025-11-27 11:29:53.385324 [INFO] manager ::
2025-11-27 11:29:53.385329 [INFO] manager :: Using MQTT broker localhost:1883
2025-11-27 11:29:53.385343 [INFO] manager :: Telemetry enabled
2025-11-27 11:29:53.390936 [INFO] everest_ctrl :: Launching controller service on port 8849
2025-11-27 11:29:53.398868 [INFO] manager :: Boot mode is set to YamlFile, loading module configs from YAML file
2025-11-27 11:29:53.398937 [INFO] manager :: Loading config file at: /home/abdulah/go-e/repo/everest-workspace/everest-core/config/config-sil.yaml
2025-11-27 11:29:53.468322 [INFO] manager :: Config loading completed in 81ms
2025-11-27 11:29:53.469752 [INFO] manager :: Starting 17 modules
2025-11-27 11:29:55.801134 [WARN] api:API void module::API::init() :: No evse energy sink configured for evse_id: 1. API module does therefore not allow control of amps or power limits for this EVSE
2025-11-27 11:29:55.801331 [INFO] api:API :: Module api initialized [2322ms]
2025-11-27 11:29:55.803011 [INFO] connector_1:Evs :: Module connector_1 initialized [2323ms]
2025-11-27 11:29:55.832473 [INFO] energy_manager: :: Module energy_manager initialized [2351ms]
2025-11-27 11:29:55.833615 [INFO] error_history:E :: Using database at "/tmp/error_history.db"
2025-11-27 11:29:55.833743 [INFO] error_history:E :: Checking database
2025-11-27 11:29:55.834323 [INFO] error_history:E :: Module error_history initialized [2353ms]
2025-11-27 11:29:55.879358 [INFO] ev_api:EvAPI :: Module ev_api initialized [2397ms]
2025-11-27 11:29:55.880671 [INFO] auth:Auth :: Module auth initialized [2399ms]
2025-11-27 11:29:55.916975 [INFO] connector_1_pow :: Module connector_1_powerpath initialized [2435ms]
2025-11-27 11:29:55.919794 [INFO] evse_security:E :: Module evse_security initialized [2433ms]
2025-11-27 11:29:55.962003 [INFO] ev_manager:EvMa :: Module ev_manager initialized [2475ms]
2025-11-27 11:29:55.962287 [INFO] iso15118_charge :: Module iso15118_charger initialized [2474ms]
2025-11-27 11:29:56.005354 [INFO] setup:Setup :: Module setup initialized [2514ms]
2025-11-27 11:29:56.007952 [INFO] grid_connection :: Module grid_connection_point initialized [2520ms]
2025-11-27 11:29:56.045776 [INFO] persistent_stor :: Module persistent_store initialized [2557ms]
2025-11-27 11:29:56.048847 [INFO] token_provider: :: Module token_provider initialized [2556ms]
2025-11-27 11:29:56.091496 [INFO] token_validator :: Module token_validator initialized [2597ms]
2025-11-27 11:29:56.092271 [INFO] slac:SlacSimula :: Module slac initialized [2602ms]
2025-11-27 11:29:56.096897 [INFO] iso15118_car :: Module iso15118_car initialized [2369ms]
2025-11-27 11:29:56.139332 [INFO] manager :: Clearing retained topics published by manager during startup
2025-11-27 11:29:56.140951 [INFO] manager :: 🚙🚙🚙 All modules are initialized. EVerest up and running [2760ms] 🚙🚙🚙
2025-11-27 11:29:56.143376 [INFO] iso15118_charge :: TCP server on wlp0s20f3 is listening on port [fe80::2a10:8294:f118:5f1a%2]:61341
2025-11-27 11:29:56.143583 [INFO] iso15118_charge :: TLS server on wlp0s20f3 is listening on port [fe80::2a10:8294:f118:5f1a%2]:64109
2025-11-27 11:29:56.146652 [INFO] evse_security:E :: Requesting leaf certificate info: V2G
2025-11-27 11:29:56.152737 [INFO] evse_security:E :: Found valid leaf: ["/home/abdulah/go-e/repo/everest-workspace/everest-core/build/dist/etc/everest/certs/client/cso/CPO_CERT_CHAIN.pem"]
2025-11-27 11:29:56.153788 [INFO] evse_security:E :: Found valid leaf: ["/home/abdulah/go-e/repo/everest-workspace/everest-core/build/dist/etc/everest/certs/client/cso/SECC_LEAF.pem"]
2025-11-27 11:29:56.187128 [WARN] iso15118_charge virtual void module::charger::ISO15118_chargerImpl::handle_update_ac_maximum_limits(types::iso15118::AcEvseMaximumPower&) :: Ignoring handle_update_ac_maximum_limits call
2025-11-27 11:29:56.220109 [WARN] iso15118_charge void {anonymous}::log_handler(openssl::log_level_t, const string&) :: <n> certificates != <n> OCSP responses
2025-11-27 11:29:56.222709 [INFO] iso15118_charge :: SDP socket setup succeeded
2025-11-27 11:29:56.229126 [WARN] auth:Auth void module::ReservationHandler::load_reservations() :: Can not load reservations because no storage was configured.
2025-11-27 11:29:56.257567 [WARN] iso15118_charge virtual void module::charger::ISO15118_chargerImpl::handle_update_ac_minimum_limits(types::iso15118::AcEvseMinimumPower&) :: Ignoring handle_update_ac_minimum_limits call
2025-11-27 11:29:56.300383 [WARN] iso15118_charge virtual void module::charger::ISO15118_chargerImpl::handle_update_ac_parameters(types::iso15118::AcParameters&) :: Ignoring handle_update_ac_parameters call
2025-11-27 11:29:56.612111 [INFO] connector_1:Evs :: AC HLC mode enabled.
2025-11-27 11:29:56.654474 [INFO] connector_1:Evs :: Ignoring BSP Event, BSP is not enabled yet.
2025-11-27 11:29:56.820101 [INFO] connector_1:Evs :: Cleaning up any other transaction on start up
2025-11-27 11:29:57.077300 [INFO] connector_1:Evs :: 🌀🌀🌀 Ready to start charging 🌀🌀🌀
2025-11-27 11:29:57.396771 [INFO] connector_1:Evs :: All errors cleared
everest-workspace $ ./everest-core/build/run-scripts/nodered-sil.sh
everest-nodered-config-volume
Successfully copied 91.6kB to everest-nodered-config-container:/data/flows.json
everest-nodered-config-container
> node-red-docker@2.2.3 start /usr/src/node-red
> node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data"
27 Nov 10:30:15 - [info]
Welcome to Node-RED
===================
27 Nov 10:30:15 - [info] Node-RED version: v2.2.3
27 Nov 10:30:15 - [info] Node.js version: v14.19.3
27 Nov 10:30:15 - [info] Linux 6.8.0-65-generic x64 LE
27 Nov 10:30:15 - [info] Loading palette nodes
27 Nov 10:30:15 - [info] Dashboard version 3.6.5 started at /ui
27 Nov 10:30:15 - [info] Settings file : /data/settings.js
27 Nov 10:30:15 - [info] Context store : 'default' [module=memory]
27 Nov 10:30:15 - [info] User directory : /data
27 Nov 10:30:15 - [warn] Projects disabled : editorTheme.projects.enabled=false
27 Nov 10:30:15 - [info] Flows file : /data/flows.json
27 Nov 10:30:15 - [warn]
---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.
If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.
You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------
27 Nov 10:30:15 - [warn] Encrypted credentials not found
27 Nov 10:30:15 - [info] Server now running at http://127.0.0.1:1880/
27 Nov 10:30:15 - [info] Starting flows
27 Nov 10:30:15 - [info] Started flows
27 Nov 10:30:15 - [info] [mqtt-broker:fc8686af.48d178] Connected to broker: mqtt://localhost:1883