Andycko
Unable to access Browserless service through private network
Thanks for the help with this, I have been using the public URL so far but I recognise it’s a very bad and potentially expensive idea since basically anyone could use my browserless instance 😳 Am I right in thinking that there is no dedicated firewall/NAT gateway setup on Raliway?
26 replies
Unable to access Browserless service through private network
Basically the same error as in the beginning
Error: connect ECONNREFUSED fd12:8e79:a9ab::3f:26ae:72f2:443 but what's changed is that the domain name has been switched for IPv6 addr26 replies
Unable to access Browserless service through private network
So I added the sleep, which fixed the issue with the startup of the node app, however the error with the connection still remains. One thing though, I added the sleep only to the node container as I'm not too sure what startup command to use with the browserless container.
26 replies
Unable to access Browserless service through private network
Interestingly enough, adding the env variable to Railway, crashed my startup command. I am using https://infisical.com/ to manage my env variables and that injects variables with the startup command like so
infisical run -- node server.js. The error being "dial tcp: lookup app.infisical.com on [fd12::10]:53: dial udp [fd12::10]:53: connect: cannot assign requested address"26 replies
Unable to access Browserless service through private network
Oh, so do you mean delay after the browserless service starts up? Sorry I meant that on every connection it needs the extra 100ms. I will try your solution, but I don't think this should be the issue then, because the service has been up for nearly an hour now. (Sorry if I'm not understanding something here)
26 replies