Open Azim-js opened 3 months ago
Were you able to solve your problem? I have exactly the same problem here. My semaphore instance is installed directly on my RHEL 9 instance. The Traggic is routed via a proxy server, but if I clone the public Git repo directly on the command line this works without any problems. So I assume that the problem is with the semaphore directly.
11:30:27 AM
Task 12 added to queue
11:30:29 AM
Started: 12
11:30:29 AM
Run TaskRunner with template: Create Switch Config
11:30:29 AM
Preparing: 12
11:32:41 AM
fatal: unable to access 'https://github.com/mmz-srf/ansible-automation.git/': Failed to connect to github.com port 443: Connection timed out
11:32:41 AM
Cloning Repository https://github.com/mmz-srf/ansible-automation.git
11:32:41 AM
Cloning into 'repository_2_5'...
11:34:52 AM
fatal: unable to access 'https://github.com/mmz-srf/ansible-automation.git/': Failed to connect to github.com port 443: Connection timed out
11:34:52 AM
Failed updating repository: exit status 128
11:34:52 AM
Running app failed: exit status 128
I ran the container in wsl2 i prolly think its something related to the network or the git in the semaphore :/
Same issue here, don't know why since some tests works fully on semaphore docker container:
I tried the ssh key and it works too.
Issue
I am able to clone the repo within the container of semaphore but from the task template it fails : But withing the container i am able to
it says couldn't resolve host name github.com with exit status 128
Impact
Ansible (task execution), Docker, Semaphore Project
Installation method
Docker
Database
MySQL
Browser
Chrome
Semaphore Version
semaphoreui/semaphore:v2.10.23-beta and latest tags
Ansible Version
Logs & errors
No response
Manual installation - system information
Did docker-compose installation
Configuration
No response
Additional information
No response