VeeamOne web port 1239 not working after upgrade to v12

[kristofjaeken]

Hello everyone,

I'm facing an issue after upgrading VeeamOne from v11 to v12 (in place upgrade). The web portal on port 1239 doesn't work anymore. However, when I look at the config in the VeeamOne settings console it says for Web Services port 2741 is set for the VeeamOne server. And indeed on port 2741 I can login to the reporting service website. Problem solved one would think. But when I want to view a report the URL switches back to port 1239 and is unable to generate/display the report.

Seems like there is a mix up with the ports used in the background and I can't figure out how to solve it. Anyone got any ideas?

Thank you!

Kristof

[RomanK]

Hello Kristof,

1239 port is the default port to access Veeam ONE Web Services, i.e. the IIS site

2741 port is used for communication with Veeam ONE internal Web API, in other words, Server <-> Web Services communication


Please open a support case and provide a case ID in this thread so we could collect all the additional details and investigate it accordingly.

Thanks

[kristofjaeken]

Hi Roman,

Thanks for the quick reply. Indeed what's on your print screens is what I see in my environment. We have a VCSP contract with a partner. I will raise a support ticket with them and take it from there.

Greetings

[kristofjaeken]

Hello,

I raised a case with our partner and they have initiated a support case with Veeam. Case number is # 07005060.
So far no solution or suggestions.

Greetings

[RomanK]

Hello Kristof,

Thanks for the case number. I can see that the case is already on the Tier 2 level.
Please continue to work with our support engineers. I'm confident they will find the cause of this issue.

Thanks

[stewsie]

Did this get resolved? I have a similar issue after upgrading from 12 to 12.1 today. I have just opened a support case

[stewsie]

I can connect on port 80 to the default IIS page

[RomanK]

Hello Paul,

As far as I can see the root cause in the case above was on the ISS side.
Could you please share your support case # as well?

Thanks

[stewsie]

07074887 I have uploaded logs and sent some screenshots as requested. I haven't reverted the snapshot, yet

[stewsie]

Another issue after the upgrade is that the native SQL backup job was still running and has used almost all the backup drive capacity. It is looking like I need to revert the snapshot on the two Veeam One servers. Not ideal

[RomanK]

Dear all,

In the case 07074887 something went wrong with certificates and the Chrome browser.

Please be aware and try multiple browsers just in case.

Thanks

[stewsie]

I am today unable to use Edge and have the same issue

[stewsie]

I am today unable to use Edge and have the same issue

Added the self signed certificate to the trusted root store in Edge and now connects OK

[stewsie]

Code: Select all

Added the self signed certificate to the trusted root store in Edge and now connects OK

Actually, I can connect to the main page that uses port 2741 but when I try to run a report this changes to use port 1239 and this fails with ERR_SSL_KEY_USAGE_INCOMPATIBLE

Firefox is now the only browser that is working.

Any suggestions? Ideally still want to use self signed certs for this service if possible

[jorgedlcruz]

Hello,
I have faced this issue before, I managed to resolve it following the next steps:


Make sure when you generate the SSL certificate, that it has the proper FQDN name the server has, etc. Never use IP for an SSL, or for connecting to VONE.

Give it a quick try, generate the SSL, restart services, and let us know.

[stewsie]

Hi Jorge. I had generated a new certificate this morning already even though the old one was still valid. Works OK in Firefox. I may need to open another support call for this. Thanks

[jorgedlcruz]

Wait one second, what version of Edge are you using? I am just seeing that others are facing similar issues, not Veeam related:
https://learn.microsoft.com/en-us/answe ... tible-micr

Does it work in Chrome, Opera, Firefox, Brave?

Ir works for me, with self-signed SSL but my Veeam ONE hostname, and the FQDN matches veeamone.jorgedelacruz.es. My Edge version is 121.0.2277.98, do you have the latest?

Let me dig more into this, we might need a workaround perhaps.

[stewsie]

I am able to connect to the Veeam One web page using 2741

After adding the certificate to Trusted Root I can connect using Chrome, Edge, and Firefox

If I then try to run a report then a new tab opens and tries to use port 1239 This is using a different certificate date than 2741. This works fully in Firefox but in Chrome and also Edge it fails

Chrome error

the website uses HSTS.

I followed info https://www.thesslstore.com/blog/clear- ... e-firefox/ to delete the site in Chrome but still get the failure

Same issue in Edge regarding HSTS

All three browsers are using the same certificate for 2741 and then the same one for 1239 both with the same hostname but different dates. Both are valid dates.

Something strange happening regarding certs

[jorgedlcruz]

Have you tried on a different computer with same browser versions?

Port 2741 should not be used by the user, it is sort of an internal port between components.

[stewsie]

Yes I have access to two PCs. I am only able to connect to 1239 using Firefox on either PC. When I connect using 1239 the certificate is different to the one when connecting to 2741 but is still valid. 1239 doesn't work on Chrome. or Edge on either PC. Edge was OK last week so I suspect an update on Edge has changed something

[stewsie]

I have opened a support case

[stewsie]

It seems that support have fixed this. The certificate in use by Veeam One did not match the one configured in IIS. Changed this to be the same as the self signed certificate in use by Veeam One all looks to be working correctly now. Apart from renewing the self signed certificate in the settings utility nothing has ever been done with certificates so it is strange that IIS was using a different Veeam self signed certificate. More testing to do but looking much better now

[jorgedlcruz]

Always happy to read a happy ending story, thanks for sharing the fix.

[kevin.boddy]

Hi,

I know this thread is a couple of weeks old now but was there any investigation done as to why the upgrade to v12.1 breaks like this?
I had exactly the same thing happen, re-generated the certificates for both the application and IIS and it worked again. There was nothing wrong with the certificates before.
Problem is my server was down for a couple of days while we worked to resolve the problem which means alerts and reports were an issue.

Is this something the is being addressed by R&D? Is there a likely-hood of this issue occurring again on the next upgrade?

Thanks
Kevin

[jorgedlcruz]

Hello Kevin,
Let me double check internally, so far I have not seen anything from QA.

Give me some time.

Thank you

[mann_brenner]

After upgrading VeeamOne from v11 to v12, the web portal on port 1239 isn't working as expected, despite configuring port 2741 in the settings console for Web Services. When attempting to view reports, it reverts to port 1239, leading to display errors. Ensure all configuration files reflect the correct port settings, restart VeeamOne services, and review firewall/proxy settings that might affect port communication. For troubleshooting "Disable HSTS settings in Chrome & Firefox, you can refer to this guide: https://cheapsslweb.com/blog/how-to-dis ... me-firefox. If issues persist, contacting Veeam support for targeted assistance with port configurations in v12 is recommended.