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

[Bug] Failed to connect - something went wrong. #455

Open
cecille opened this issue Oct 3, 2024 · 2 comments
Open

[Bug] Failed to connect - something went wrong. #455

cecille opened this issue Oct 3, 2024 · 2 comments
Labels

Comments

@cecille
Copy link

cecille commented Oct 3, 2024

Describe the bug

image

Steps to reproduce the behavior

This seems to happen randomly. Sometimes running stop then start fixes it. It appears to be related to not having internet access on the TH when started? possibly?

Expected behavior

nothing goes wrong. But also that there's a way to recover. We have a way to recover, at the very least that should be documented here. I was told to re-install the TH from scratch and that took HOURS and the error came back almost immediately. Luckily, an ATL knew how to fix it, but the error is cryptic.

Log files

No response

PICS file

No response

Screenshots

No response

Environment

No response

Additional Information

No response

@cecille cecille added Bug Something isn't working Needs Triage Found_SVE_1.4 labels Oct 3, 2024
@fabiowmm
Copy link
Contributor

@cecille what was the ATL workaround? cycle start?

@cecille
Copy link
Author

cecille commented Oct 10, 2024

ATL workaround is to run stop then start, but also ensure that there is internet access, not just local network access either when start was run or when you first connect to the TH. I wasn't clear on when it was required, and didn't have time to attempt a repro for both cases.

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

No branches or pull requests

2 participants