Skip to main content
Solved

Veeam ONE web interface - internal error - v12


MavMikeVBR
Forum|alt.badge.img+1

Veeam has recently been upgraded from 11a to v12. Post upgrade we cant get into the web interface for Veeam ONE. Client app works….

I’ve checked IIS, local logs etc, cant see anything….

anyone seen this?

 

 

Best answer by MavMikeVBR

looks like since v12 upgrade, the port has changed to 2741. 

https://VEEAMOneWebClientFQDN:2741

this solved the issue

View original
Did this topic help you find an answer to your question?

Chris.Childerhose
Forum|alt.badge.img+21

Check that the services are running and ensure that VeeamDCS.exe process is climbing for memory usage.  You might need to give it slightly more time to get going as I have seen this as well then just wait a bit and it works.


MavMikeVBR
Forum|alt.badge.img+1
  • Influencer
  • September 28, 2023

thanks Chris. I will check this but Veeam processes have been running for some time. The VONE client works ok. I might bring down Veeam completely, restart then check the process you mentioned and make sure its consuming memory. 


Chris.Childerhose
Forum|alt.badge.img+21

Hope it helps.  I know this can be finicky so give it time to get going before trying to log in to the web UI.  🤞🏼


MavMikeVBR
Forum|alt.badge.img+1
  • Influencer
  • September 28, 2023

thanks Chris, will keep you posted….


Forum|alt.badge.img
  • Comes here often
  • October 2, 2023

I already had this problem in the past.
In my case was the veeam one came with an express SQL that only supports 10 GB of data. So i needed to connect in the Veeam one server click in the icon of Veeam One Client > Settings > Server Settings > Other > Support Utility > Click Launch > General> Retention Policy Period > Change the policy to a lower numb and apply retention.
Note: If you change from 1 year retention to 3 Months you’ll only have 3 months of history.


MavMikeVBR
Forum|alt.badge.img+1

looks like since v12 upgrade, the port has changed to 2741. 

https://VEEAMOneWebClientFQDN:2741

this solved the issue


Chris.Childerhose
Forum|alt.badge.img+21
MavMikeVBR wrote:

looks like since v12 upgrade, the port has changed to 2741. 

https://VEEAMOneWebClientFQDN:2741

this solved the issue

Glad to hear you resolved the issue.


Comment