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
describe the bug
Upon a fresh restart of my desktop, Screenpipe will open with a recording status and then immediately switch to red. Rebooting the software from tray or task manager do not seem to fix it. Logs report that the port is busy.
I looked at my port usage with netstat and the only thing occupying port 3030 is a Docker process with a Screenpipe parent. I've tried killing the process, rebooting Screenpipe, and rebooting Windows 11 and this happens everytime. If I run via CLI with a custom port, it will work briefly before finding the same error.
system info
os: windows 11
screenpipe version: 0.2.23
additional context
add any other context, screenshots, or error logs here.
In the CLI, I enabled verbose Rust backtrace logging and this is what I get:
Lastly, this may or may not be unrelated, but Screenpipe is inable to find monitors or audio devices in the UI, but the logs do reflect that they are seen.
The text was updated successfully, but these errors were encountered:
describe the bug
Upon a fresh restart of my desktop, Screenpipe will open with a recording status and then immediately switch to red. Rebooting the software from tray or task manager do not seem to fix it. Logs report that the port is busy.
I looked at my port usage with netstat and the only thing occupying port 3030 is a Docker process with a Screenpipe parent. I've tried killing the process, rebooting Screenpipe, and rebooting Windows 11 and this happens everytime. If I run via CLI with a custom port, it will work briefly before finding the same error.
system info
additional context
add any other context, screenshots, or error logs here.
In the CLI, I enabled verbose Rust backtrace logging and this is what I get:
Lastly, this may or may not be unrelated, but Screenpipe is inable to find monitors or audio devices in the UI, but the logs do reflect that they are seen.
The text was updated successfully, but these errors were encountered: