Skip to content
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

Unable to connect to the server: Forbidden #21695

Closed
birajdarabhishek1 opened this issue Dec 21, 2018 · 8 comments
Closed

Unable to connect to the server: Forbidden #21695

birajdarabhishek1 opened this issue Dec 21, 2018 · 8 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@birajdarabhishek1
Copy link

birajdarabhishek1 commented Dec 21, 2018

I have installed Minishift with Proxy setting.
The server is accessible via web console at:
https://192.168.42.76:8443/console

You are logged in as:
User: developer
Password:

To login as administrator:
oc login -u system:admin

Issue:
[root@minishift ~]# oc status
Unable to connect to the server: Forbidden

[root@minishift ~]# oc login -u system:admin
error: Forbidden

[root@minishift ~]# curl https://192.168.42.76:8443/console
curl: (56) Received HTTP code 403 from proxy after CONNECT

How can I connect console from my VM, or Outside Network.

#minishift #Linux

@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 21, 2019
@RashaHaj
Copy link

RashaHaj commented Mar 31, 2019

I'm running into the same issue , trying to install openshift cluster. Eventually, the cluster is indeed deployed

[root@master openshift-master]# oc version
oc v3.11.0+62803d0-1
kubernetes v1.11.0+d4cacc0
features: Basic-Auth GSSAPI Kerberos SPNEGO
Unable to connect to the server: Forbidden

but I'm unable to excute any of the commands without having the output

[root@master playbooks]# oc get nodes
Unable to connect to the server: Forbidden

@birajdarabhishek1 May you tell me how you fix it please?

@openshift-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci-robot openshift-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Apr 30, 2019
@openshift-bot
Copy link
Contributor

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci-robot
Copy link

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@xxxvodnikxxx
Copy link

/reopen

@openshift-ci-robot
Copy link

@pavenova: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@xxxvodnikxxx
Copy link

Issue is still in place (oc client v 3.11)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

5 participants