Open new case online with Firefox

[JeWe]

Hi,

when I try to open a new support case with Firefox (19.0.2), the buttons for uploading log files are gone. With Internet Explorer 10 everything is fine.

Regards

[Vitaliy S.]

Hello,

Thanks for pointing this our, I will forward this information to our webteam.

Thanks!

[asckey]

The problem is the iFrame embedding the upload page is narrower than the upload page, which has a minWidth set.

If you have the FireBug extension installed, you can work around the issue by inspecting the page in FireBug, finding the <iframe> tag and changing the scrolling="no" attribute to "yes" to allow you to scroll to the Upload button. (That's how I just uploaded some logs to a support case I raise this morning.)

[masonit]

I have the same problem with Chrome. Looks fine in IE 9.

\Masonit

[comeandtakeit]

Same issue here. It's borderline shameful to have your customers load up IE to get something done on the website.

[davidb1234]

I reported this several times to Veeam support staff and was pretty much insulted and told I didn't know what I was doing trying to open cases....

In my case it was Chrome that doesn't work.

[Gostev]

@David could you please let me know your support case ID, as all communications are being recorded - I would like to have our Director of support to review your situation. Thanks!

@All I just tried the whole process with clean Firefox 19.0.2 install, and I do not observe the above-mentioned issue. Kindly please include the screenshot of the issue you are seeing. Make sure you clean browser cache before trying, or force-reload the page (Ctrl-F5).

[JeWe]

Cool, seems to be fixed now...

@Gostev: Now it's working, before it didn't. I surely had my browser cache cleared before trying it as I'm kind of paranoid and let Firefox clear the cache automatically when shutting it down. As asckey said, there was obviously a workaround. And as others reported the error also, don't believe that there are only stupid users. However, works for me now...

[Shralok]

I was having this issue, but it is now resolved.

The issue I am having now is that *.veeam.com is SLLLOOOOOOOOOOWWWWWWWWWWWWWWWWWWWWW