Replace this template with your information

*Describe your question in as much detail as possible: Hello everyone, I have to develop the next environment, gitlab local, jenkins local and wildfly, I have gitlab and jenkins in the same virtual machine running. Now in my development enviroment in local (windows 10 pro) I have visual studio and I am trying to push my proyect to the gitlab in the Debian VM but it is imposible, in the first time show me 407 error , proxy and fighting a lot that error gone but now told me the next error “fatal: unable to access ‘’: The requested URL returned error: 503” and I don´t waht to do

  • *What are you seeing, and how does it differ from what you expect to see?
    I was seeing configuration with ping, I put a repositry public in the gitlab local but nottjing.
  • Consider including screenshots, error messages, and/or other helpful visuals
    If anyone need screenshot tell me about that
  • What version are you on (Hint: /help) ? and are you using self-managed or
    gitlab 15.5 ce, visual studio 1.7.82 and jenkins 2.346.3
  • What troubleshooting steps have you already taken? Can you link to any docs or other resources so we know where you have been?
    restart jenkins restart gitlab config visual studio but what is 503 error? don´t access to server but the access is there.

Thanks for taking the time to be thorough in your request, it really helps! :blush:
Thanks to all people.

The Idea is make the development in local, up it to gitlab and that it was detected by jenkins and it deploy it in to a wildfly server… Hard work.

Best regards.

The very first word in the template you used is Replace, why didn’t you? It gets a lot harder to read when we all have to filter out the template stuff.

It’s unclear (to me at least) what you have actually done. Maybe someone else can untangle it, but my suggestion would be to start over with a fresh VM and install GitLab on that.

Why are you using an old version of GitLab (15.5 is 10 months old, 16.3 is the newest).

Try to take jenkins and visual studio out of the equation and focus on getting a connection from (a browser on) your workstation to your GitLab server.

Then you can get connections from visual studio working (I’ve never used that, but I can’t see why that would be hard, but m$ has a way of making everything hard),
Then finally get connections working between GitLab and Jenkins (other people in the company managed, so I also guess that is simple - but all their usage of Jenkins were migrated to GitLab years ago).