-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Localhost refused to work #41
Comments
Getting the same error on both arc browser and chrome and I have turned off all security warnings. |
Thanks for reporting.
|
1.Can you access http://localhost:8501/ ?
|
The only error in my docker logs
|
@arafatkatze do you know if you're using dualstack ipv6/ipv4 docker?
|
I am using ipv4
And both the curl commands return successfully though
|
I had the same issue; restarting the container fixed it. |
Solved for me now after re starting the container for the second time |
Have the same problem on my environment but restarting is not fixing it. |
Thank you for reopening the issue. |
I added some thoughts here #141 since I couldn't make this work I will perhaps just make a separate VM and run this on it https://github.com/suitedaces/computer-agent/tree/main To me it seems like the essence of the issue is that docker's port are not "showing up" and I can't do the port forwarding to my machine so perhaps I can just run a cheap VM on AWS and run the project above on it. |
Port is showing up. Page is kind of loading so there is definitely a
Webserver listening at the port.
Ara ***@***.***> schrieb am Do., 31. Okt. 2024, 11:35:
… I added some thoughts here #141
<#141> since I
couldn't make this work I will perhaps just make a separate VM and run this
on it https://github.com/suitedaces/computer-agent/tree/main
To me it seems like the essence of the issue is that docker's port are not
"showing up" and I can't do the port forwarding to my machine so perhaps I
can just run a cheap VM on AWS and run the project above on it.
—
Reply to this email directly, view it on GitHub
<#41 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABV67O6AIDCSZ2G2EHI623TZ6IBYLAVCNFSM6AAAAABQM34NY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBZGUZTONBTGA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
For me restarting the whole computer and deleting chrome history specifically somehow worked right now but not sure how that happened. |
I will give it a try
Ara ***@***.***> schrieb am Fr., 1. Nov. 2024, 14:33:
… For me restarting the whole computer and deleting chrome history
specifically somehow worked right now but not sure how that happened.
—
Reply to this email directly, view it on GitHub
<#41 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABV67O6LJJOTUMLP7GEJEPTZ6N7LZAVCNFSM6AAAAABQM34NY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJRHA4DAOJYG4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
It's not #147 <-- this issue, is it? |
ok fixed it by:
full cmd:
|
Docker logs for me are perfectly okay
And also my anthropic key is fine too(Tested wtih a curl request that worked fine).
The text was updated successfully, but these errors were encountered: