-
Notifications
You must be signed in to change notification settings - Fork 296
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
Address is not accessible #253
Comments
@MultiPath thanks for sharing the issue. Will make sure to get you up and running soon. On your remote server have you tried to run BTW, please make sure the long_dir path you specify is the parent dir of your log dirs. So it looks something like this: |
Please make sure that port You can use
|
Hi @MultiPath I was wondering if you were able to get it working? |
I have the same problem and tried different ports, it does not work. This maybe a bug |
We are looking into it. |
Could you check if this answer solves the issue? Please make sure to upgrade Aim. |
Hi, after updating the aim version. Now it returns me new errors:
I am not sure why it said permission denied. |
Hi @MultiPath, sorry for a relatively slow reply - took our time to investigate this issue. A strange issue never seen before. This would help to eliminate the problem for other users too. 🙏 |
Hi @MultiPath, We just released v2.5.0. No more docker required to run Aim! Try it out by installing the latest version |
Closing this issue due to inactivity. |
Hi,
I am sorry for another maybe basic question which I cannot find doc or explanation from the README.
When I tried
aim up --tf_logs <my_location> --host localhost --port 10008
It directly returned me
Is it related to firewall? Or some setting I must do before launching it?
I originally thought it was functioned similarly as tensorboard and I am trying the same way.
My log files are located in a remote server, I tried to run aim at the server for some port, and I will forward it to my local machine's local port so that I can open it in a browser.
Thank you very much
The text was updated successfully, but these errors were encountered: