Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to reconnect after Companion restart on MacOS #23

Open
ChrisSW58 opened this issue Dec 28, 2024 · 8 comments
Open

Unable to reconnect after Companion restart on MacOS #23

ChrisSW58 opened this issue Dec 28, 2024 · 8 comments

Comments

@ChrisSW58
Copy link

ChrisSW58 commented Dec 28, 2024

Describe the bug
On MacOS, when Companion is stopped and restarted, screendesk cannot reconnect even though all the settings are the same. Stuck on Trying to connect. Stopping it trying to connect and re-saving the settings has no effect.

To Reproduce
Stop Companion and restart

Expected behavior
screendesk should reconnect with the existing settings

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS:MacOS Sequoia 15.3
  • Version [e.g. 22] screendesk 1.1.0

Additional context
Only way around I have found is to uninstall and reinstall screendesk - even a restart does not fix the issue. Nice app by the way - well done! 👏🏻

@ChrisSW58 ChrisSW58 changed the title BUG - Unable to reconnect after Companion restart on MacOS Unable to reconnect after Companion restart on MacOS Dec 28, 2024
@josephdadams
Copy link
Owner

Quitting ScreenDeck and reopening after companion is running - does that work?

@josephdadams
Copy link
Owner

Oh. You said it doesn’t. Sorry. This is interesting. I’m not experiencing that on my end. Is companion running locally or somewhere else on the network?

@ChrisSW58
Copy link
Author

Oh. You said it doesn’t. Sorry. This is interesting. I’m not experiencing that on my end. Is companion running locally or somewhere else on the network?

Thanks for prompt reply - Locally - 127.0.0.1:8000

@josephdadams
Copy link
Owner

Same here. What version of Companion?

@ChrisSW58
Copy link
Author

Latest beta - 3.5.0 7659

@josephdadams
Copy link
Owner

I'm not seeing it on that version or greater either. Could there be a firewall or similar in effect?

@ChrisSW58
Copy link
Author

Interesting - and I would think that if that were the case it would not run at all. It runs very well when first installed... If you can't recreate it I would suggest closing this. If I find out any further information that could be useful, I'll let you know....

@josephdadams
Copy link
Owner

Let's keep it open for a while and see if anyone else is experiencing it also.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants