You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After ensuring there is only a single instance running (there are five processes started), it may take many tries to start up the service through cast-web-api-desktop and there are two kinds of errors that are possible at this stage. After hitting start and a few seconds of "Loading", the dialog will show "online" but without an IP address, meaning it didn't actually work. A few seconds later one of the following errors appears. The number of attempts to start before it will be running properly varies from 2 to several, it's not consistent:
First error is: "API doesn't respond. Check the log file to see the error message."
There are no error messages in the log, just:
"cast-web-api v1.2.1
cast-web-api running at http://192.168.1.2:3000"
This error may repeat after another try and eventually you get the second error:
"Uncaught Error: ENOENT: no such file or directory, open 'C:\Users\mark\AppData\Roaming\cast-web-api-desktop\logs\1576506403936.log'"
The log file is actually there, accessible, and has the exact same message in it.
Next attempt may result in the API doesn't respond message again, and after a few more attempts it will start properly.
The text was updated successfully, but these errors were encountered:
Version 1.21, Windows:
After ensuring there is only a single instance running (there are five processes started), it may take many tries to start up the service through cast-web-api-desktop and there are two kinds of errors that are possible at this stage. After hitting start and a few seconds of "Loading", the dialog will show "online" but without an IP address, meaning it didn't actually work. A few seconds later one of the following errors appears. The number of attempts to start before it will be running properly varies from 2 to several, it's not consistent:
First error is: "API doesn't respond. Check the log file to see the error message."
There are no error messages in the log, just:
"cast-web-api v1.2.1
cast-web-api running at http://192.168.1.2:3000"
This error may repeat after another try and eventually you get the second error:
"Uncaught Error: ENOENT: no such file or directory, open 'C:\Users\mark\AppData\Roaming\cast-web-api-desktop\logs\1576506403936.log'"
The log file is actually there, accessible, and has the exact same message in it.
Next attempt may result in the API doesn't respond message again, and after a few more attempts it will start properly.
The text was updated successfully, but these errors were encountered: