Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

"Last Delivery Not Successful Service Timeout" in RTC GitHub integration (RTC 6.02)

Questions
Tags
Users
Badges
Sean Burke
(378●10●144●247) edited
Feb 07 '17, 12:29 p.m.

Getting a service timeout error setting up the GIT RTC integration.  Using https://xxxx.xx.org/ccm/service/com.ibm.team.git.common.internal.IGitHubInvokeService?repoKey=6aa0f5cd96a24ad1901a023716817f40&repoKey=XXXXXXX



I don't think I need to add any thing under Services but I did anyways.  

0 votes

1 answer
2,937 views
0 votes

One answer

Permanent link
Sreerupa Sen
FORUM MODERATOR / JAZZ DEVELOPER (1.0k●4) Feb 07 '17, 10:30 p.m.

 Are you able to access the RTC server from GitHub? Is this GitHub enterprise or the public version? If it's the public version, then you may not be able to access your RTC server unless it's publicly accessible as well.


Cheers
--Rupa

0 votes

Comments
Ryan McBryde
Oct 31 '17, 6:00 p.m.

Sreerupa,

I have the same error coming from my GitHub Enterprise webhook when trying to communicate with my RTC server, both of which are only accessible after connecting to our company VPN.  I don't know for sure but I am assuming that they are behind the same firewall.  I am working on verifying that assumption.  If they are, then do you have any other suggestions?

Thank you

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Ask a question
Guidelines
FAQ
Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 12,020

Question asked: Feb 07 '17, 12:28 p.m.

Question was seen: 2,937 times

Last updated: Oct 31 '17, 6:00 p.m.

Confirmation Cancel Confirm