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

Enforce Attended Access not working Agent #618

Closed
Kilian-Schwarz opened this issue Apr 13, 2023 · 6 comments · Fixed by #624
Closed

Enforce Attended Access not working Agent #618

Kilian-Schwarz opened this issue Apr 13, 2023 · 6 comments · Fixed by #624
Assignees

Comments

@Kilian-Schwarz
Copy link

Hello all,
I have the problem with the Enforce Attended Access that I can't press yes or no. I can't press yes.

On the client the agent is installed.
On the server remotely via docker.

Enforce Attended Access is enabled and the request comes to the client but when I press yes or no nothing happens when I look on the server via tcp dump also no packets come from the client when I press yes or no

@bitbound bitbound self-assigned this Apr 14, 2023
@rucksman
Copy link

rucksman commented Apr 17, 2023

Same goes for me. Agent is installed on Windows 11 Pro. When the notification pops up on the client machine I can move and close and minimize this notification window, but nothing happing when clicking "Yes" or "No". Only the background color for the buttons changes.

@simonreufsteck
Copy link

Same problem here

@MaciejStiller
Copy link

Can confirm it also happens for me on server&agent v2023.04.17.1215

@bitbound
Copy link
Contributor

This should be fixed in the changes I'm working on now. I'll comment again when a preview image is available. Probably sometime next week.

@bitbound
Copy link
Contributor

This should be fixed in the experimental tag:

docker pull immybot/remotely:experimental

I'll keep this open until the latest image is updated. Probably next week. I'll also do a GitHub release at the same time.

@bitbound bitbound linked a pull request May 3, 2023 that will close this issue
@bitbound
Copy link
Contributor

bitbound commented May 3, 2023

This should be fixed in the latest release.

@bitbound bitbound closed this as completed May 3, 2023
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

Successfully merging a pull request may close this issue.

5 participants