faas: Use of CLI or Web UI returns status code 500 and 'Get : unsupported protocol scheme ""'
My actions before raising this issue
- Followed the troubleshooting guide
- Read/searched the docs
- Searched past issues (there was an issue closed yesterday because it didn’t follow this template)
Expected Behaviour
Access to the Web UI or via faas-cli after installation should be successful.
Current Behaviour
Access to the web UI returns the body: Get : unsupported protocol scheme "" with status code 500. Using faas-cli commands such as login or list return the response: Server returned unexpected status code: 500 - Get : unsupported protocol scheme ""
Possible Solution
It looks like something is overriding the router in gateway/server.go. Even browsing to <host>:8080/system/info with a GET request returns the same error message.
Steps to Reproduce (for bugs)
- Install OpenFaaS on Raspbian (with Docker managed by Portainer) using
./deploy-stack - Services successfully start and are running.
- Browse (or run CLI commands) to the OpenFaaS port.
- Encounter error message.
Context
N/a
Your Environment
- FaaS-CLI version ( Full output from:
faas-cli version):
CLI: commit: 893972afffa5ea6672faa6e11743ae46322ec58c version: 0.9.2
-
Docker version
docker version(e.g. Docker 17.0.05 ): 19.03.1 -
Are you using Docker Swarm or Kubernetes (FaaS-netes)? Docker Swarm
-
Operating System and version (e.g. Linux, Windows, MacOS): Linux (Raspbian)
-
Code example or link to GitHub repo or gist to reproduce problem: N/a
-
Other diagnostic information / logs from troubleshooting guide
Next steps
You may join Slack for community support.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 16 (10 by maintainers)
This was a trivial fix to the ps1 script, will raise a PR shortly.
I, personally, have no issue with removing it. But, I don’t use windows. If the bash script works just as well on windows, then I say, get rid of the powershell script
I’ll check either tomorrow morning at the weekend - and will comment if the issue is not resolved 🙂 thanks for the speedy fix!
Thanks. I’ve been able to reproduce. Portainer is a red herring.
Seems this is being triggered:
https://github.com/openfaas/faas/blob/6481b683f233c39f2f724a7a6318e445c4176b8c/gateway/handlers/external_auth.go#L27
I’ve got a fix lined up. Shouldn’t be too long…