Jump to content

Sam

Members
  • Content Count

    33
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Sam

  • Rank
    Advanced Member

Recent Profile Visitors

1,637 profile views
  1. Your certificate is valid, but your issuer's is not, perhaps your issuer stopped its services like our did 3 months ago.
  2. Hi Carlos, I finally deleted all the wrong commits by hand. Hopefully all the changesets numbers were consecutive (even all was mixed up in the timeline) so it was not that hard to detect them. There's a protection against two GitRepos to be synced on one Plastic repo, not against what I did by mystake : two PlasticRepos synced with the same GitRepo, moreover one of the two PlasticRepo was a submodule of the other PlasticRepo. Thanks for help
  3. Hi Carlos, The sub-repo synced with github is OK, but it's the "parent" plastic repo that has been accidentally sinced with github mirror image of its child repo. There is no github image of the parent repository. Perhaps there's a way to detect all the commit that come from gitsync and delete them ? Sincerly Sam T.
  4. Hi everybody, I'm afraid I did a big mistake on one of my repo. I have a repo called "My_repo_A" which has a XLinked sub repo called "My_repo_A_shares". This sub repo "My_repo_A_shares" is synced with a repo on github. But tonight, after a hard work week, I synced by mistake the parent repo "My_repo_A" with the same repo on github. That resulted in a warning like "the branches have to be merged before being able to push with gitsync again ...". Hopefully there are no problems on github, but in plastic a lot of commits are duplicated with different guid, and branches have two heads ... So ... the winner is me ! I know ... but is there a way to cancel a gitsync ? Thanks a lot for your help.
  5. We finally found the problem : the issuer of our certificate does not exists anymore, and its own certificate (that certify it was a trusted CA) was no more valid. I use the command : openssl s_client -connect dyn.my-sample-domain.com :8088 -showcerts That resulted on : verify error:num=20:unable to get local issuer certificate So we just regenerated a new certificate from another CA ( https://www.sslforfree.com/ that uses Let's Encrypt) and the problem was solved A huge thanks to Carlos from Plastic SCM support team, who gave me the keys to locate and solve this (not-Plastic) issue.
  6. I confirm that the problem is also present out of office, directly without the host redirection. I will send a message to the support I'll keep you in touch
  7. Thanks for the precisions, perhaps this could help someone else on this forum. The "check connection" produces the same error message. I connect to my server with the domain name as I always did : ssl://dyn.my-sample-domain.com:8088 I will make another test out of my office (without the line in host file). At the moment the line is present, and ... the problem too ! I'll keep you in touch with the result of test. And, if there is no good news, I'll send the log file to support. Sincerly Samuel T.
  8. Hello, Sorry to be a little bit insistant, but I really need a solution. My small company is really impacted by this problem as we can't commit/checkout on one of our most used computer. Thanks a lot for help
  9. Hello everybody, I suddently have a problem with one of my Plastic SCM client on Windows. Everything worked well, but since last week I can't connect to my Plastic server anymore. Nothing changes in server config nor in my client config, but now I've got this message "The remote certificate is not valid according to the validation procedure" (see attached picture). The server has an attached domain with a valid, not expirated, certificate. But, as my client is on the same network as the server and as my box can't do loopback (domain name pointing to itself) I have an entry in my client host file to redirect domain name to local server IP address. This worked for more than 3 years without problem. The only thing that happened last week is that I used my PC out of office, so I removed the redirect line in my client host file in order to do my commit through "real" internet. This also worked properly. But a few hours later when I restarted Plastic from my office again (with local host redirection), it began to display the error message. Server and clients were in version 7.0.16.2604, I updated my Windows client to 8.0.16.3068 but the problem did not disappear. Two other clients (on Mac) don't suffer from the problem and continu to reach the server without problem, locally or through internet. So my question is : is there a kind of certificate cache on Windows client ? ... Perhaps wrong data was cached when I came back to my office. I tried to clear windows ssl state in "internet options" but it had no effect. Any idea ?
×
×
  • Create New...