-
Notifications
You must be signed in to change notification settings - Fork 322
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
Securing Aim Remote Tracking server using SSL key and certificate #3172
Comments
@JeroenVranken thanks for the issue. This could be related to the auth token things we have added recently. @mihran113 @alberttorosyan what do you guys think? |
Any update on this ? I guess I faced a similar issue in #3206 |
This error occurs with version 3.20.1, but everything works fine when I revert to the 3.17.4 version of AIM |
Have you tried the latest version |
@erikdao did you manage to resolve it? It seems in general Aim docs could be improved for making it into production. The docker-compose file is missing even in the repo, and there are a few docker / ssl related issues open for a long time.. |
It turned out that my problem was different. I didn't enable SSL when deploying Aim Server. My problem was related to networking on GCP. |
Hey folks! Sorry for late response. I've opened a PR which will add support for self-signed SSL certificates. This addition will allow to specify cert files path via env variable, which will allow the client flow to work as expected. The changes will be included in the upcoming |
@mihran113 amazing, thank you very much!! |
Hey folks the changes for this have been published with the newest release of Let me know if everything works as expected or not 🙌 |
Securing Aim Remote Tracking server using SSL key and certificate
Hi, first of all I appreciate all the work you've put into making Aim!
I am having some trouble securing the connection to the Aim Remote Tracking (RT) Server, and was wondering if you could help me out.
I recently setup a virtual machine on Azure, which is running both the Aim RT Server and the Aim UI. To do this, I have used a
docker-compose.yml
, which brings up both the server and the UI. This is working properly, I can log runs from another machine and see them appear in the UI, great.However, now I want to secure the connection to the remote tracking server using SSL, as described here. I've created a self-signed key and certificate file using openssl, as described here.
Whenever I bring up the server using this command, eveything seems in working order, I do not get any errors etc:
But then when I try to log a run from another machine, I get the following error on the client:
Do you have any clue as to why this is not working? Here is the
docker-compose.yaml
and the python file I'm using:The text was updated successfully, but these errors were encountered: