You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just performed fresh install using the documented instructions below:
Containers fail to start due to the included certificate having expired in August 2022:
_netpalm-controller_1 | redis.exceptions.ConnectionError: Error 1 connecting to redis:6379. [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired (ssl.c:1131).
Please update documentation on the repo to include the additional step below:
Ensure you first have docker installed
sudo apt-get install docker.io
sudo apt-get install docker-compose
Just performed fresh install using the documented instructions below:
Containers fail to start due to the included certificate having expired in August 2022:
_netpalm-controller_1 | redis.exceptions.ConnectionError: Error 1 connecting to redis:6379. [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired (ssl.c:1131).
Please update documentation on the repo to include the additional step below:
Ensure you first have docker installed
sudo apt-get install docker.io
sudo apt-get install docker-compose
Clone this repository
git clone https://github.com/tbotnz/netpalm.git
cd netpalm
Regenerate certificates <--- New Step
./redis_gen_new_certs.sh
After the container has been built and started, you're good to go! netpalm will be available on port 9000 under your docker hosts IP.
Not sure if this the best way but it worked for me.
Additional improvement suggestions:
Would it be possible for the compose script to automatically recreate the certificate upon each new build?
Could steps be documented to explain how an admin can provide their own certificates if auto-regeneration is not possible/preferred?
It looks as though the regen script puts the certs into the below location:
/netpalm/netpalm/backend/core/security/cert/tls
Thanks
Lee
The text was updated successfully, but these errors were encountered: