-
Notifications
You must be signed in to change notification settings - Fork 455
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
Access API Server 502 after using HTTPS proxy #751
Comments
@zryfish Please help to resolve the problem. |
Please check if it still exists in 3.0.0 @zryfish |
Can you give more specific details? What's ther error message, what's your proxy configuration looks like? |
Nginx settings:
Request: Request URL: https://kubesphere.xxxx.com/api/v1/nodes/master1 |
The old version 2.0.2 is correct |
It's problem with websocket setttings. delete sesetion:
or:
|
proxy_ssl_server_name on; |
* feat: add interval hooks Signed-off-by: elichen95 <[email protected]> * fix: fix use actions bugs Signed-off-by: elichen95 <[email protected]> * feat: add Object input and properties input component Signed-off-by: elichen95 <[email protected]> * feat: add TimeSelector component Signed-off-by: elichen95 <[email protected]> * fix: fix detail left side styles Signed-off-by: elichen95 <[email protected]> * feat: export Inputs and TimeSelector components Signed-off-by: elichen95 <[email protected]> --------- Signed-off-by: elichen95 <[email protected]>
General remarks
Describe the bug
Using Nginx as a reverse proxy, when configured for HTTPS access, All /api/xx requests report 502 errors, But /kapis/xxx are fine。Using ip:30880 is also correct。
For UI issues please also add a screenshot that shows the issue.
Versions used(KubeSphere/Kubernetes)
KubeSphere: 2.1.0
Kubernetes: (If KubeSphere installer used, you can skip this)
Environment
How many nodes and their hardware configuration:
3 masters: 2cpu/4g
3 nodes: 4cpu/16g
(and other info are welcomed to help us debugging)
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
The console supports HTTPS proxy access
The text was updated successfully, but these errors were encountered: