Open johnjbarton opened 5 years ago
Carlo is intercepting all the network requests and as Chrome goes for https://domain/*, carlo feeds it with the resources from the file system / dynamic handler / some other proxied web location. In some cases, the error you see would be there due to zombie chrome instances from the previous ndb launches.
I had same issue when I "pkg" a nodejs app using carlo. Though I don't know why, but I changed app.serveFolder(__dirname);
to app.serveFolder('.');
, then this error disappeared.
When trying to run
ndb
, acarlo
app, in a linux environment with some restrictions I fail with net::ERR_NAME_NOT_RESOLVED and the carlo window shows the chrome sad page icon withdomain's server IP address could not be found
.The issue is related to the URL set here: https://github.com/GoogleChromeLabs/carlo/blob/4e8ed7bdfe656f4c2672ab777ab81df777b2b185/lib/carlo.js#L349
Obviously 'domain' is not a real DNS name. How is this supposed to work?