tacticalrmm
tacticalrmm copied to clipboard
Cannot upgrade Docker - Followed instructions
Server Info (please complete the following information):
- OS: Debian 12
- Browser: Chrome, Firefox, Edge
- RMM Version (as shown in top left of web UI): v0.15.12
Installation Method:
- [ ] Standard
- [x] Docker
Agent Info (please complete the following information):
- Agent version (as shown in the 'Summary' tab of the agent from web UI):
- Agent OS: Windows 10 and 11
Describe the bug Cannot upgrade Docker, no matter what I have tried I always get 502 error on login after upgrade. I then roll everything back to original version and it works fine. Tried this on all versions since the v0.16 was release, I have not tried on v0.16.4 yet, but .3 did not work.
I have tried using three different browsers and their incognito/private windows also. Clearing cache, and just plain waiting a couple days...
To Reproduce Steps to reproduce the behavior: Follow procedure in documentation exactly.
Expected behavior Will work afterward after login
output of the following please
docker -v
docker-compose -v
fix will be in next release
Great news, what is the next release number?
On Fri, Sep 29, 2023 at 3:33 AM 'Dan' via Justin's extended aliases < @.***> wrote:
fix will be in next release
— Reply to this email directly, view it on GitHub https://github.com/amidaware/tacticalrmm/issues/1623#issuecomment-1740513734, or unsubscribe https://github.com/notifications/unsubscribe-auth/AATO6ZI6LQRKVLEMKEOF3ITX42BUFANCNFSM6AAAAAA4MLRGKQ . You are receiving this because you authored the thread.Message ID: @.***>
It will be 0.16.5 I am planning to release it this weekend
I just tried the upgrade and I am still receiving the 502 error... Following instructions exactly as posted:
Here is what I get from Chrome:
Request URL: https://api.REPLACED.net/checkcreds/
Request Method: POST
Status Code: 502 Bad Gateway
Remote Address: REPLACED:443
Referrer Policy: strict-origin-when-cross-origin
Access-Control-Allow-Credentials: true
Access-Control-Allow-Origin: https://rmm.REPLACED.net
Content-Length: 559
Content-Type: text/html
Date: Wed, 04 Oct 2023 13:45:16 GMT
Server: nginx/1.24.0
Vary: Origin
:authority: api.REPLACED.net
:method: POST
:path: /checkcreds/
:scheme: https
Accept: application/json, text/plain, */*
Accept-Encoding: gzip, deflate, br
Accept-Language: en-US,en;q=0.9
Content-Length: 55
Content-Type: application/json
Origin: https://rmm.REPLACED.net
Referer: https://rmm.REPLACED.net/
Sec-Ch-Ua: "Google Chrome";v="117", "Not;A=Brand";v="8", "Chromium";v="117"
Sec-Ch-Ua-Mobile: ?0
Sec-Ch-Ua-Platform: "Linux"
Sec-Fetch-Dest: empty
Sec-Fetch-Mode: cors
Sec-Fetch-Site: same-site
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/117.0.0.0 Safari/537.36
Thanks again for your help!!!
On Fri, Sep 29, 2023, 10:29 AM 'Dan' via Justin's extended aliases < @.***> wrote:
It will be 0.16.5 I am planning to release it this weekend
— Reply to this email directly, view it on GitHub https://github.com/amidaware/tacticalrmm/issues/1623#issuecomment-1741077711, or unsubscribe https://github.com/notifications/unsubscribe-auth/AATO6ZKTK3BVD54JIKRGLX3X43SNHANCNFSM6AAAAAA4MLRGKQ . You are receiving this because you authored the thread.Message ID: @.***>
Just wondering if anyone has any idea's. I cannot upgrade my Docker still.... Fails with the message above.
Can you paste some container logs so we can see the errors? 502 just means services are not running but we need to find out why.
Thanks. I will try the upgrade again and post the container logs.
On Wed, Oct 18, 2023 at 1:53 AM 'Dan' via Justin's extended aliases < @.***> wrote:
Can you paste some container logs so we can see the errors? 502 just means services are not running but we need to find out why.
— Reply to this email directly, view it on GitHub https://github.com/amidaware/tacticalrmm/issues/1623#issuecomment-1767786501, or unsubscribe https://github.com/notifications/unsubscribe-auth/AATO6ZNVBSS5Y3CMJXVPQWDX754FBAVCNFSM6AAAAAA4MLRGKSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRXG44DMNJQGE . You are receiving this because you authored the thread.Message ID: @.***>