I'm running windows 10. I used to use github just fine and I'm not sure what changed, but I can't access the site in any way. I can't browse it. I can't use github tools. I've tried http and https. It all times out.
All other https sites work fine. All other sites that I can find in general work fine. It's just me and Github not getting along.
I beseech thee, code gurus, help me get back to work.
I've tried setting myself in the DMZ of my router and turning off the firewall, to no effect.
are you about to connect to this ip?
192.30.252.153
192.30.252.154
You should get this page
Comment on whether you get this or not you get this so I can help you
It went away as mysteriously as it came. We may never know.
Related
I have had a Github account for about 3-4 months. Just today, I added an 'Organization'. I changed the security settings for this Organization, and now it says 'No Restrictions'. Here's an image.
I followed the instructions from the link below, to get that setup.
https://docs.github.com/en/free-pro-team#latest/github/setting-up-and-managing-organizations-and-teams/enabling-oauth-app-access-restrictions-for-your-organization
Now, I am trying to link Keroku to my Github account. In the Keroku environment, I click 'Connect to Github' and I get this.
I followed the instructions in the link below.
https://www.youtube.com/watch?v=GgNcs9zlFSA
Somehow, the lady can connect in 2.5 minutes, but even after working on this for 60 minutes, all I get is error saying Keroku can't connect to Github. Does anyone know exactly how this works?
Thanks.
This is very, very bizarre. I tried the same steps in Google Chrome and everything worked just as I expected it to. For some weird reason, I couldn't get it to work in Firefox. Anyway, everything works fine now.
While trying to clone a Git repository in Eclipse Luna, I'm getting the error shown below using the https link:
I added the said values in the Git configuration using this link - "SSL host could not be verified" error but I'm still getting the same error.
I'm sure that the URL is correct. Not too sure if there's something wrong with proxy settings (I don't think so).
On the other hand, I tried the ssh link by generating keys and putting them into the enterprise gitlab account and also on the pc (windows) but I'm still being unsuccessful doing that and getting the same error shown in the image below except for the last point.
I checked the error log, while using the https link it says 'not authorized' and 'Auth fail' when I try to use the ssh link.
I'm listed as the member of the repository and I'm using my email and password of the enterprise account to access it, but no luck.
Help much appreciated. Thank you.
First, if you are using a private GitHub Enterprise in an enterprise, SSH URLS are rarely allowed.
For HTTPS URLs, you need to make sure your proxy configuration ignore host setting in Eclipse includes the domain name of the GitHub Enterprise (on premise) private server, or it will try to contact the proxy every time (and fail)
I have face same problem. To resolve this problem make sure your repository access level is public. It will solve this issue.
Assuming that your company uses their own certificate authority, their root certificate has most probably been added to your computer's trust store. However, Java by default uses its own trust store, so Eclipse does not know about it.
The best solution is to make Eclipse use the system trust store. See this answer for Windows or this answer for macOS.
As part of the setup to use the Workflow Service in Bluemix, a plugin is required, added to your DevOps project associated with Workflow. The "install plugin" pre-populates the Orion install plugin field with:
https://workflow.ng.bluemix.net/workflow/devOpsServices/workflowPlugin.html
After a minute or so, this consistently times out with:
Plugin handshake timeout for: http://workflow.ng.bluemix.net/workflow/devOpsServices/workflowPlugin.html
As you can see, the timeout is on an http:// url rather than https:// , this being consequential or relevant, I'm unsure.
I did also try a straight http:// url instead with the same effect. Also, different computer, same steps, same result.
Any additional troubleshooting come to mind?
TIA
we tried to reproduce the issue but it seems as the issue is gone and the whole installation worked for us in Google Chrome. Do you still encounter the issue? Please retry. What you're describing seems like an endless loop redirecting http to https. If you still encounter the problem, please let us know, and we'll continue with our investigations. Regards, R.
My TFS is working fine for: http://localhost:8081 (notification URL).
But my other domain: www.sub.mysite.com (example), which succesfully resolves to other sites inside my IIS, will simply not load up TFS. Basically it sits on "connecting" then eventually times out.
What I don't understand is, when I change the URL in the TFS Admin console, I've noticed it doesn't even update the IIS bindings.
What can I do?
This could be the the old double-hop issue? But I can't really tell as the question isn't specific.
This issue came after #EricLaw explained me what was the problem when I could not receive a response back from my REST request.
Essentially the request was just returning blank, then I found out that if Fiddler was not running,
the application works just fine.
As Eric explains there are some security issues that I should consider when developing/debugging in Windows Server 2012.
I followed the instructions and installed the suggested utility but when I click in the AppContainer Loopback utility I get the following error: Failed to get AppContainer info: Unable to enumerate AppContainer, Is the windows Firewall Service started?
Of course, my Firewall Service is working just fine.
Additionally there is something I still don't understand, why my HTTP request works just fine whenever Fiddler is not running anyway?
Has anyone had this problem already?
PS: we need a new tag called fiddler4
I know it is a bit late to bring this up, but since I had a fix I though it might be helpful to others, too.
I used the utility described here and although it did not fix the issue for me, it had a glowing hint, the Windows Firewall.
What fixed the issue for me was starting Windows Firewall service, which I had disabled previously.
Hope this might help.