I've setup the BrowserStack TeamCity plugin in our Windows TeamCity Server (TCS) but the actual work is carried out by a Linux TeamCity Agent (TCA). Both of those machines are whitelisted in our AWS WAF (W) when accessing our staging environment (S).
When the automated Cucumber tests are running using that tunnel they constantly hit "403 Forbidden". However when I use a manually constructed tunnel (using code and the browserstack-local npm package) from the TCA machine (via SSH) all works fine and the S environment is accessible.
For now I've setup out TeamCity configurations to use the browserstack-local npm package specifically to access the S environment but the other environments are tested OK using the BrowserStack TeamCity plugin setup. These environments do NOT have any W rules against them.
This is an obscure scenario but I was able to isolate this to this plugin. Every other scenario works when accessing the S environment.
I've setup the BrowserStack TeamCity plugin in our Windows TeamCity Server (TCS) but the actual work is carried out by a Linux TeamCity Agent (TCA). Both of those machines are whitelisted in our AWS WAF (W) when accessing our staging environment (S).
When the automated Cucumber tests are running using that tunnel they constantly hit "403 Forbidden". However when I use a manually constructed tunnel (using code and the browserstack-local npm package) from the TCA machine (via SSH) all works fine and the S environment is accessible.
For now I've setup out TeamCity configurations to use the browserstack-local npm package specifically to access the S environment but the other environments are tested OK using the BrowserStack TeamCity plugin setup. These environments do NOT have any W rules against them.
This is an obscure scenario but I was able to isolate this to this plugin. Every other scenario works when accessing the S environment.