-
Notifications
You must be signed in to change notification settings - Fork 43
NIECONN_REFUSED: Unable to create new online repository #269
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
Comments
did you go through the note, https://docs.abapgit.org/user-guide/getting-started/troubleshooting.html#_411-connection-failed ? |
Hi, We have seen , its not helpful |
did you try the https://docs.abapgit.org/user-guide/setup/ssl-test.html ? |
Hi, same error from above ABAP Program too |
It's not ABAP but a general network error. Your basis team has to check the connection on the operating system of the ABAP application server first. For example try to ping github.com. Then curl the repo URL with port 443. If you want to write to a repo, api.github.com must work too. Also ask them if there's a proxy the requests must go through and if the proxy requires user/password. These things must work first before using the SSL test program makes sense. |
Please let me know option to authorized |
You are trying to update abapGit repository directly. This is not allowed. It would work with one of your own repositories. To request an update for abapGit, you first have to create a fork on GitHub, then change the URL of the repo in abapGit in your system. Now you can stage and commit changes to your fork (recommended to use a new branch). When done, create a pull request in GitHub from your fork to the original abapGit repository. The community will review the changes and provide feedback. |
Please guide to get access |
Do you work for Wiley? Well I have to help because your company has books like Marvel Universe for Dummies! Very cool 😎 403 error means that you are missing permissions to change the repository. The "write" permission must be added to your user (or token). That's done in the settings of the repo on GitHub. |
I have created myself as an Admin, assigned all roles. Please check and let me know path you provide WRITE access if missing |
Your fork repo is private so I can't see details (https://github.com/wiley/abapGit -> 404). When you add the repo in abapGit, you should use the main branch (not EMP). The path for checking access is https://github.com/wiley/abapGit/settings/access. When you stage changes, then create a new branch and commit changes to it. |
That message is from your system and the ADT plugin for abapGit. We can't help with that |
Hi Team,
Please check below issue while create creating new online repository for abapGit configuration.
Used prog : ZABAPGIT_STANDALONE from SE38 in SAP ABAP editor
Error: HTTP error 411 occurred: Direct connect to github.com:443 failed: NIECONN_REFUSED(-10)
SAP BASIS team opens firewall and 443 port too.
reference for abapGit configuration :
https://developers.sap.com/tutorials/abap-environment-abapgit..html
https://docs.abapgit.org/user-guide/setup/ssl-setup.html
Please check and revert back with solution at earliest.
Regards,
Nag
The text was updated successfully, but these errors were encountered: