-
- Influencer
- Posts: 13
- Liked: 1 time
- Joined: Dec 29, 2010 9:26 am
- Contact:
Problem after updating to new 1.0.0.267
I ran the update to 1.0.0.267 that was showing in the GUI - it warned that it might take some time...
3hrs later the VM appears unresponsive, the URL generates a "This site can't be reached *.*.*.* refused to connect...."
Is there something I should do to get this going again?
3hrs later the VM appears unresponsive, the URL generates a "This site can't be reached *.*.*.* refused to connect...."
Is there something I should do to get this going again?
-
- Product Manager
- Posts: 5797
- Liked: 1215 times
- Joined: Jul 15, 2013 11:09 am
- Full Name: Niels Engelen
- Contact:
Re: Problem after updating to new 1.0.0.267
Did you try to restart the VM already? If the issue persists, please contact our support and let us know the case ID for future reference.
Personal blog: https://foonet.be
GitHub: https://github.com/nielsengelen
GitHub: https://github.com/nielsengelen
-
- Influencer
- Posts: 13
- Liked: 1 time
- Joined: Dec 29, 2010 9:26 am
- Contact:
Re: Problem after updating to new 1.0.0.267
Same after restart - I'll contact support
-
- Influencer
- Posts: 13
- Liked: 1 time
- Joined: Dec 29, 2010 9:26 am
- Contact:
Re: Problem after updating to new 1.0.0.267
Case ID # 04560094
-
- Service Provider
- Posts: 14
- Liked: 1 time
- Joined: Nov 01, 2010 8:10 pm
- Full Name: Mike Mitchell
- Contact:
Re: Problem after updating to new 1.0.0.267
I am experiencing the exact same issue! I updated and the GUI will not launch. I restarted the VM, and I can SSH into it, but still no GUI. I opened case# 04560751.
-
- Influencer
- Posts: 13
- Liked: 1 time
- Joined: Dec 29, 2010 9:26 am
- Contact:
Re: Problem after updating to new 1.0.0.267
My case is ongoing, Veeam Support are currently examining log files.
Also running the free version - I'll post back when I hear back from Veeam Support
Also running the free version - I'll post back when I hear back from Veeam Support
-
- Service Provider
- Posts: 14
- Liked: 1 time
- Joined: Nov 01, 2010 8:10 pm
- Full Name: Mike Mitchell
- Contact:
Re: Problem after updating to new 1.0.0.267
How do I collect log files to submit to the case?
-
- Influencer
- Posts: 13
- Liked: 1 time
- Joined: Dec 29, 2010 9:26 am
- Contact:
Re: Problem after updating to new 1.0.0.267
I'd open your own case with Veeam Support and maybe reference case ID (#04560094) so at least they know that there's more than one instance of this issue.
-
- Product Manager
- Posts: 5797
- Liked: 1215 times
- Joined: Jul 15, 2013 11:09 am
- Full Name: Niels Engelen
- Contact:
Re: Problem after updating to new 1.0.0.267
@fmagic Support will assist you if u can’t get the logs.
Personal blog: https://foonet.be
GitHub: https://github.com/nielsengelen
GitHub: https://github.com/nielsengelen
-
- Lurker
- Posts: 2
- Liked: 1 time
- Joined: Oct 14, 2020 4:12 am
- Full Name: Wesley
- Contact:
Re: Problem after updating to new 1.0.0.267
Encountered a different weird issue today.. jobs are failing with error Azure storage error: Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature. ())
Just logged a support ticket on this issue Case #04568795
Just logged a support ticket on this issue Case #04568795
-
- Service Provider
- Posts: 14
- Liked: 1 time
- Joined: Nov 01, 2010 8:10 pm
- Full Name: Mike Mitchell
- Contact:
Re: Problem after updating to new 1.0.0.267
I saw that error ("...Server failed to authenticate...", too, but then it ran fine the next day.
Also, regarding the original question, support did help me with the repair of the installation with the .deb file, and everything is back to normal again.
Also, regarding the original question, support did help me with the repair of the installation with the .deb file, and everything is back to normal again.
Who is online
Users browsing this forum: No registered users and 4 guests