{"action":"created","issue":{"url":"https://api.github.com/repos/zalando/zalenium/issues/437","repository_url":"https://api.github.com/repos/zalando/zalenium","labels_url":"https://api.github.com/repos/zalando/zalenium/issues/437/labels{/name}","comments_url":"https://api.github.com/repos/zalando/zalenium/issues/437/comments","events_url":"https://api.github.com/repos/zalando/zalenium/issues/437/events","html_url":"https://github.com/zalando/zalenium/issues/437","id":296380146,"number":437,"title":"Protractor Port Config","user":{"login":"geek876","id":3296763,"avatar_url":"https://avatars0.githubusercontent.com/u/3296763?v=4","gravatar_id":"","url":"https://api.github.com/users/geek876","html_url":"https://github.com/geek876","followers_url":"https://api.github.com/users/geek876/followers","following_url":"https://api.github.com/users/geek876/following{/other_user}","gists_url":"https://api.github.com/users/geek876/gists{/gist_id}","starred_url":"https://api.github.com/users/geek876/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/geek876/subscriptions","organizations_url":"https://api.github.com/users/geek876/orgs","repos_url":"https://api.github.com/users/geek876/repos","events_url":"https://api.github.com/users/geek876/events{/privacy}","received_events_url":"https://api.github.com/users/geek876/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-02-12T13:47:46Z","updated_at":"2018-02-14T07:30:47Z","closed_at":null,"author_association":"NONE","body":"Hi,\r\nWe running Zalenium within K8s which works as expected (the starting of containers etc).\r\nWe use gitlab-ci (also using kubernetes-runner) builds and protractor\r\nPreviously, we were using browser-stack but now as most of our tests are Chrome, we want to use Zalenium.\r\nWithin Protractor config, our baseurl is set to http://localhost:3000 (https://github.com/angular/protractor/blob/master/lib/config.ts)\r\nThe tests do get executed via Zalenium on a K8S docker node, however all tests fail. When we see the recording, we see that the browser is trying to open http://localhost:3000 but it says 'This site can't be reached'. I suspect, there is some port that needs to open between the CI build container (the container that runs tests/protractor) and the Zelinum HUB ? \r\nThe exact configuration works without issues on browser stack and there, if we see recordings, we do actually see the site loading up on http://localhost:3000"},"comment":{"url":"https://api.github.com/repos/zalando/zalenium/issues/comments/365519394","html_url":"https://github.com/zalando/zalenium/issues/437#issuecomment-365519394","issue_url":"https://api.github.com/repos/zalando/zalenium/issues/437","id":365519394,"user":{"login":"diemol","id":5992658,"avatar_url":"https://avatars1.githubusercontent.com/u/5992658?v=4","gravatar_id":"","url":"https://api.github.com/users/diemol","html_url":"https://github.com/diemol","followers_url":"https://api.github.com/users/diemol/followers","following_url":"https://api.github.com/users/diemol/following{/other_user}","gists_url":"https://api.github.com/users/diemol/gists{/gist_id}","starred_url":"https://api.github.com/users/diemol/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/diemol/subscriptions","organizations_url":"https://api.github.com/users/diemol/orgs","repos_url":"https://api.github.com/users/diemol/repos","events_url":"https://api.github.com/users/diemol/events{/privacy}","received_events_url":"https://api.github.com/users/diemol/received_events","type":"User","site_admin":false},"created_at":"2018-02-14T07:30:47Z","updated_at":"2018-02-14T07:30:47Z","author_association":"MEMBER","body":"Hi @geek876,\r\n\r\nThis is usually only a matter of configuration. When running a test and the browser is inside a container, if you say http://localhost:3000, then `localhost` will be inside the container, and not where your app is actually running.\r\n\r\nYou could check the docs: https://zalando.github.io/zalenium/#docker, the section called \"Accessing the host\". Which basically means that the browser needs to access the url where your app is running.\r\n\r\nIn the case of BrowserStack, it works because you are probably opening a tunnel from the machine where your app is running, and that's why it can access it.\r\n\r\nLet us know how it goes, I'll keep this issue open for a few days in case you have feedback for us."}}
{"actor":{"display_login":"diemol"}}