Mocks do not work - multiple endpoints

Get Support
21

Hi npsoftware , please update the runner and try again. thank you.

22

as stated, it does not show the arrow, that there is an update available

23

now it does. sorry

24

but still, why it does not work on self-hosted?

25

docker run --name edim-jenkins-dev1
-e TZ=Europe/Vienna
-e SERVER_APP_BASE_URL=https://api.eu.apidog.com
-e TEAM_ID=2204
-e RUNNER_ID=12
-e ACCESS_TOKEN=TSHGR-OljTX8t2AiMaRY8pcTqN6_wecIVHdhn6
-p 80:4524
-v “/opt/apidog/runner”:/opt/runner
-d apidog/self-hosted-general-runner
Using default tag: latest
latest: Pulling from apidog/self-hosted-general-runner
1f3e46996e29: Pull complete
37892ffbfcaa: Pull complete
5650d6de56fd: Pull complete
6504e29600c8: Pull complete
7c744546a863: Pull complete
7e683dcef604: Pull complete
5d0f25a079ab: Pull complete
a287fd3ab684: Pull complete
76b7720d84b8: Pull complete
1b71c6fb6e99: Pull complete
Digest: sha256:8500457580aa28170b228d2e8a14e8f812d6d3a3b6872f72d401e2b36c661e0b
Status: Downloaded newer image for apidog/self-hosted-general-runner:latest
docker.io/apidog/self-hosted-general-runner:latest
90a543f5b0f8c9e8243870937511029cd063126f3a18fb79a33118ef43a92aac
docker: Error response from daemon: driver failed programming external connectivity on endpoint edim-jenkins-dev1 (a39329a8ccbcd4cab0767c4e65a04a52746e8a4fddfab34bb451eb239088e5c9): failed to bind port 0.0.0.0:80/tcp: Error starting userland proxy: listen tcp4 0.0.0.0:80: bind: address already in use.

26

where is the problem?

27

As per the error message, your port is already occupied and please use another one or kill the port and try again.

28

ok. now the runner is updated, but I get this:
{
“message”: “Runner has received a mock call, but it seems that there are some issues with the network environment of the Runner.”
}

29

bey installing the docker image for runner I used
-p 4524
instead of -p 80:4524 as the 80 was used already. is that ok so?

30

As per the error message, your runner server network environment can not access our Apidog server. can you try with different network?

31

ok. I had to deploy the runner with a -p 4524:4524 instead of 80:4524 and on 80, the nginx server was listening

32

now it seems to work

33

thanks

34

you are right