We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
ngrok problem
docker run on local lan I try to expose to internet and get Bad Request
But, when I expose ollama server 11434 port, it works, only port 443 don't works
ngrok http http://localhost:443
Forwarding https://xxxxx.ngrok-free.app -> http://localhost:443
400 Bad Request The plain HTTP request was sent to HTTPS port nginx/1.27.1
08:45:11.267 UTC GET / 400 Bad Request 08:45:11.453 UTC GET /favicon.ico 400 Bad Request
expose 443
ngrok expose 443
ubuntu
No response
The text was updated successfully, but these errors were encountered:
Hey @zinwelzl! 👋 Thanks for flagging this bug! 🐛🔍
You're our superhero bug hunter! 🦸♂️🦸♀️ Before we suit up to squash this bug, could you please:
📚 Double-check our documentation: https://rengine.wiki 🕵️ Make sure it's not a known issue 📝 Provide all the juicy details about this sneaky bug
Once again - thanks for your vigilance! 🛠️🚀
Sorry, something went wrong.
https works
No branches or pull requests
Is there an existing issue for this?
Current Behavior
ngrok problem
docker run on local lan
I try to expose to internet and get Bad Request
But, when I expose ollama server 11434 port, it works, only port 443 don't works
ngrok http http://localhost:443
Forwarding https://xxxxx.ngrok-free.app -> http://localhost:443
400 Bad Request
The plain HTTP request was sent to HTTPS port
nginx/1.27.1
Connections ttl opn rt1 rt5 p50 p90
2 0 0.22 0.36 0.01 0.01
HTTP Requests
08:45:11.267 UTC GET / 400 Bad Request
08:45:11.453 UTC GET /favicon.ico 400 Bad Request
Expected Behavior
expose 443
Steps To Reproduce
ngrok expose 443
Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: