Eric Uldall

That's weird. I'm having a similar issue except when I manually check the challenge path I get a good response. Any more ideas here? **UPDATE:** I deleted the kube-lego pod...

I'm also interested to know if this is possible. Or perhaps we can have the node-port that the ingress maps to then create a secondary service of type LoadBalancer? **TL;DR**...

I've just confirmed that a secondary service of type LoadBalancer works fine. Here's how I will use this in my configuration... ``` apiVersion: v1 kind: Service metadata: name: echoserver-failover namespace:...

For anyone else that comes here looking for vue 3 support, this won't work. There's at least 1 problem, vue3 no longer support assigning globals to Vue.prototype.$var Stackoverflow explaining the...

big +1 to figuring this out. GA is pretty much useless without the ability to identify where your traffic is coming from.

Would the following documentation: ``` gtag('set', 'campaign', { 'id': 'abc.123', 'source': 'google', 'medium': 'cpc', 'name': 'spring_sale', 'term': 'running+shoes', 'content': 'logolink' }); ``` Be implemented in api/pageview as: ``` event('set', 'campaign',...

Sent a PR, any feedback is appreciated: https://github.com/MatteoGabriele/vue-gtag/pull/517

Same issue and I noticed there seems to be an issue loading the env in server-worker-loader ``` import 'http:/localhost:3000/@vite/env'; import 'http://localhost:3000/crx-client-worker'; ``` It's built with `http:/` missing the second forward...

Fixing that doesn't seem to resolve the issue. I get a cors error in chrome extension logs: ``` Access to script at 'http://localhost:3000/crx-client-worker' from origin 'chrome-extension://gcnpefeokmmfpfbihpigfjmiancnjnhi' has been blocked by...

found my issue. Had something running on port 3000 in docker. Vite is not port aware against non vite process' it seems.