[GH-ISSUE #933] Remote reboot not working after update to 0.11.2 #572

New issue

Closed

opened 2026-03-02 02:17:20 +03:00 by kerem · 5 comments

kerem commented

2026-03-02 02:17:20 +03:00

Owner

Originally created by @bvessey on GitHub (Jan 13, 2022).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/933

Originally assigned to: @wh1te909 on GitHub.

Server Info (please complete the following information):

OS: Ubuntu 20.04
Browser: Tried with Chrome & Firefox, assume all browsers same behavior
RMM Version (as shown in top left of web UI): 0.11.2

Installation Method:

[X ] Standard
Docker

Agent Info (please complete the following information):

Agent version (as shown in the 'Summary' tab of the agent from web UI): 1.8.0
Agent OS: Windows 10 Enterprise, 64 bit v1909 (build 18363.1977) • Agent v1.8.0 || Windows 10 Enterprise, 64 bit v1909 (build 18363.2037) • Agent v1.8.0

Describe the bug
A clear and concise description of what the bug is.
I am no longer able to invoke / trigger a reboot of the client PC from the context / actions menu in TacticalRMM's web interface.

To Reproduce
Steps to reproduce the behavior:
1 - Right-click on asset
2 - Select Reboot > Now from Menu
3 - Observe nothing happening on client device...

Expected behavior
Previously this would trigger a reboot of the remote asset within 10 seconds or so.

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

Additional context
Add any other context about the problem here.

Originally created by @bvessey on GitHub (Jan 13, 2022). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/933 Originally assigned to: @wh1te909 on GitHub. **Server Info (please complete the following information):** - OS: Ubuntu 20.04 - Browser: Tried with Chrome & Firefox, assume all browsers same behavior - RMM Version (as shown in top left of web UI): 0.11.2 **Installation Method:** - [X ] Standard - [ ] Docker **Agent Info (please complete the following information):** - Agent version (as shown in the 'Summary' tab of the agent from web UI): 1.8.0 - Agent OS: Windows 10 Enterprise, 64 bit v1909 (build 18363.1977) • Agent v1.8.0 || Windows 10 Enterprise, 64 bit v1909 (build 18363.2037) • Agent v1.8.0 **Describe the bug** A clear and concise description of what the bug is. I am no longer able to invoke / trigger a reboot of the client PC from the context / actions menu in TacticalRMM's web interface. **To Reproduce** Steps to reproduce the behavior: 1 - Right-click on asset 2 - Select Reboot > Now from Menu 3 - Observe nothing happening on client device... **Expected behavior** Previously this would trigger a reboot of the remote asset within 10 seconds or so. **Screenshots** If applicable, add screenshots to help explain your problem. **Additional context** Add any other context about the problem here.

kerem

2026-03-02 02:17:20 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-02 02:17:21 +03:00

Author

Owner

@bvessey commented on GitHub (Jan 13, 2022):

Additional info:

Just attempted to schedule the reboot and it returns the following error:

@bvessey commented on GitHub (Jan 13, 2022): Additional info: Just attempted to schedule the reboot and it returns the following error: ![image](https://user-images.githubusercontent.com/23658345/149387792-a3647044-2257-4ff5-8a0c-d30730b3d6b4.png)

kerem commented

2026-03-02 02:17:21 +03:00

Author

Owner

@bvessey commented on GitHub (Jan 13, 2022):

Forgot to mention, am using hardening instructions from docs
https://wh1te909.github.io/tacticalrmm/securing_nginx/

Had to comment out server_names_hash_bucket_size 256; in /etc/nginx/conf.d/botblocker-nginx-settings.conf as it was indicating that the directive was duplicated.

@bvessey commented on GitHub (Jan 13, 2022): Forgot to mention, am using hardening instructions from docs https://wh1te909.github.io/tacticalrmm/securing_nginx/ Had to comment out server_names_hash_bucket_size 256; in /etc/nginx/conf.d/botblocker-nginx-settings.conf as it was indicating that the directive was duplicated.

kerem commented

2026-03-02 02:17:21 +03:00

Author

Owner

@wh1te909 commented on GitHub (Jan 13, 2022):

thanks will fix and do another release today

@wh1te909 commented on GitHub (Jan 13, 2022): thanks will fix and do another release today

kerem commented

2026-03-02 02:17:21 +03:00

Author

Owner

@bvessey commented on GitHub (Jan 13, 2022):