Vesta Control Panel - Forum

Current Vesta CP version: 1.0.0
Previous Vesta CP version:0.9.8-26
OS Version: Ubuntu 18.04 LTS / CentOS 7
Browser Version: Firefox 94.0.2 (64-bit) / Safari Version 15.1 (16612.2.9.1.30, 16612)

I am facing the following issues after the upgrade to 1.0.0. I have tried installing on Ubuntu 18.04 LTS and CentOS 7.
1. After login, the page only displayes the top Menu List. The detailed Elements for the Menu items are not displayed on the page.
2. Tried many times with Refresh, but every time the session logged out.
3. Multiple times tried with deleting the cache and the cookies, the same blank page is displayed every time I login again.
4. If at all the first page is displayed correctly after multiple retries, then on clicking on the next menu item, the contents disappear again.

Could someone throw light on the issue? How can I resolve this ? Any suggestions.
NOTE: Today I tried with Vesta CP 1.0.0-5, still facing the same issue.

We are also having the same issue here...

After the new interface update of Vesta (v.1) logging in is a marathon of clearing caches, cookies, opening and closing browsers, trial & error. This is really intermittent, sometimes all goes well, sometimes it is just impossible to have the screens after logging in. It's like the session cookie is not properly set and the React interface won't load the different sections. We can use the Users, Web, Mail, etc links at the top, but sections load empty. When refreshing the page, we are taken back to the login page. After logging back in, the sections come empty again.

We haven't been able to pinpoint the exact cause so far... one possible cause might have something to do with multiple browsers trying to log into Vesta with the same user. So far, the best solution is to login as another vesta user, log out and try again as the original user. This works... most of the time.

This happens not only on current servers, but also on any new installation of Vesta V1.x, whether on Ubuntu 18.04, 18.10, Debian 9, Centos 7...

It is surprising that there is little reports of this issue... Anyone else experiencing this?