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
bug: The web return something went wrong when navigating to a remote server's IP #2838
Comments
@kian-zhao Have you tried the solution in this #2806 |
I have updated API_BASE_URL as my remote server IP in the .yml file like http://xxx.xxx.xx.xx:1337, but it returned the same thing when I open the remote server IP. Can you give me some example that I can't open the link in the #2806 ? Maybe I make something wrong but I don't realize it. @zytoh0 |
i have setup the application on premise using https://jan.ai/docs/server-installation/onprem NVIDIA GPU with CUDA Toolkit 11.7 or higher I am assuming that is a typo and that NVIDIA is only needed if you are using the GPU/NVIDIA options. Please confirm that my assumption about minimum requirements is correct I am running app_cpu_fs option I changed API_BASE_URL to http://mypublicaddress:1337 However in looking in the Google Chrome console I get several errors af this url: curl -v -L http://mypublicaddress:1337 gives me the Swagger page just fine. I cannot access anything /v1 curl -v -L http://mypublicaddress:1337/v1/app/invokeExtensionFunc is an error. curl -v -L http://mypublicaddress:1337/v1/app/invokeExtensionFunc
< HTTP/1.1 404 Not Found
Google console: Errors are repeated several times:
invokeExtensionFunc @ 872-642984574cb5f955.js:2789 |
similar to many errors like: #2895 |
Describe the bug
I've started a jan by docker running on-prem on a remote server, but when I connect to the IP, it shows that something went wrong, such as "Loading chunk 345 failed","Loading chunk 786 failed".
Steps to reproduce
Steps to reproduce the behavior:
I've followed the steps as well as https://jan.ai/docs/server-installation/onprem, and running by "sudo docker compose --profile cpu-fs up -d". I've try both default IP and my public IP address.
Screenshots
Environment details
The text was updated successfully, but these errors were encountered: