Keep Got Logout After Update to 0.98.22 ?

[yoko eagle]

I notice few days ago I can't navigate within Vesta control panel. It keep redirect me to the login page after 2 - 3 clicks. Firstly I thought it was just temporary problem with my internet provider network changing ips but today the problem still persistent when I want to create new site.
I use subdomain with cloudflare flexible SSL for the login page. Also I enabled autoupdate and it seems like it happen after the latest version 0.98 release 22 ?
Never experienced this before.
Have tried:

Code: Select all

apt-get update && apt-get upgrade

v-update-sys-vesta-all

reboot

Still no luck any clue?

From /usr/local/vesta/log/nginx-error.log

Code: Select all

2018/04/09 16:29:34 [emerg] 23066#0: listen() to 0.0.0.0:8080, backlog 511 failed (98: Address already in use)
2018/04/09 16:29:34 [emerg] 23066#0: listen() to 0.0.0.0:8080, backlog 511 failed (98: Address already in use)
2018/04/09 16:29:34 [emerg] 23066#0: listen() to 0.0.0.0:8080, backlog 511 failed (98: Address already in use)
2018/04/09 16:29:34 [emerg] 23066#0: listen() to 0.0.0.0:8080, backlog 511 failed (98: Address already in use)
2018/04/09 16:29:34 [emerg] 23066#0: listen() to 0.0.0.0:8080, backlog 511 failed (98: Address already in use)
2018/04/09 16:29:34 [emerg] 23066#0: still could not bind()
2018/04/09 16:32:21 [emerg] 23331#0: listen() to 0.0.0.0:8080, backlog 511 failed (98: Address already in use)
2018/04/09 16:32:21 [emerg] 23331#0: listen() to 0.0.0.0:8080, backlog 511 failed (98: Address already in use)
2018/04/09 16:32:21 [emerg] 23331#0: listen() to 0.0.0.0:8080, backlog 511 failed (98: Address already in use)

From log /usr/local/vesta/log/error.log

Code: Select all

2018-04-09 15:45:56 v-restore-user  'admin' 'admin.2014-01-14.tar' [Error 3]
2018-04-09 15:47:05 v-restore-user  'admin' 'admin.2014-01-14.tar' [Error 3]
2018-04-09 15:47:37 v-restore-user  'admin' 'moved_from_vesta2.tar' [Error 10]
2018-04-09 15:48:10 v-restore-user  'admin' 'moved_from_vesta2.tar' [Error 10]
2018-04-09 15:48:57 v-restore-user  'admin' 'moved_from_vesta2.tar' [Error 10]
2018-04-09 15:50:36 v-restore-user  'admin' 'moved_from_vesta2.tar' [Error 10]
2018-04-09 15:51:09 v-restore-user  'admin' 'moved_from_vesta2.tar' [Error 10]
2018-04-09 15:51:23 v-restore-user  'admin' 'moved_from_vesta2.tar' [Error 10]
2018-04-09 15:53:08 v-restore-user  'admin' 'moved_from_vesta2.tar' [Error 10]
2018-04-09 15:58:30 v-restore-user  'admin' 'admin.2018-04-09_11-37-40.tar' [Error 3]
2018-04-09 15:58:30 v-restore-user  'admin' 'admin.2018-04-09_11-37-40.tar' [Error 3]
2018-04-09 15:58:30 v-restore-user  'admin' 'admin.2018-04-09_11-37-40.tar' [Error 3]
2018-04-09 15:58:32 v-restore-user  'admin' 'admin.2018-04-09_11-37-40.tar' [Error 3]
2018-04-09 15:58:35 v-restore-user  'admin' 'admin.2018-04-09_11-37-40.tar' [Error 3]
2018-04-09 15:58:35 v-restore-user  'admin' 'admin.2018-04-09_11-37-40.tar' [Error 3]
2018-04-09 15:58:38 v-restore-user  'admin' 'admin.2018-04-09_11-37-40.tar' [Error 3]
2018-04-09 15:58:38 v-restore-user  'admin' 'admin.2018-04-09_11-37-40.tar' [Error 3]
2018-04-09 15:58:39 v-restore-user  'admin' 'admin.2018-04-09_11-37-40.tar' [Error 3]
2018-04-09 15:58:40 v-restore-user  'admin' 'admin.2018-04-09_11-37-40.tar' [Error 3]
2018-04-09 15:58:40 v-restore-user  'admin' 'admin.2018-04-09_11-37-40.tar' [Error 3]
2018-04-09 15:58:40 v-restore-user  'admin' 'admin.2018-04-09_11-37-40.tar' [Error 3]
2018-04-09 15:58:42 v-restore-user  'admin' 'admin.2018-04-09_11-37-40.tar' [Error 3]
2018-04-09 15:59:06 v-restore-user  'admin' 'admin.2018-04-09_11-37-40.tar' [Error 3]
2018-04-09 15:59:19 v-restore-user  'admin' 'admin.2018-04-09_11-37-40.tar' [Error 3]
2018-04-09 15:59:19 v-restore-user  'admin' 'admin.2018-04-09_11-37-40.tar' [Error 3]
2018-04-09 15:59:21 v-restore-user  'admin' 'admin.2018-04-09_11-37-40.tar' [Error 3]
2018-04-09 15:59:29 v-restore-user  'admin' 'admin.2018-04-09_11-37-40.tar' [Error 3]
2018-04-09 19:52:27 v-start-service  [Error 1]
2018-04-09 19:52:40 v-start-service  [Error 1]
2018-04-09 19:53:10 v-start-service  'firewall' [Error 20]
2018-04-09 19:54:07 v-start-service  'firewall' [Error 20]

From /usr/local/vesta/log/system.log

Code: Select all

2018-04-09 13:53:42 v-add-cron-vesta-autoupdate
2018-04-09 14:03:37 v-delete-firewall-ban  '52.170.5.151' 'SSH'
2018-04-09 14:05:21 v-add-firewall-chain  'SSH'
2018-04-09 14:05:21 v-add-firewall-ban  '52.170.5.151' 'SSH'
2018-04-09 14:12:39 v-add-firewall-chain  'SSH'
2018-04-09 14:12:39 v-add-firewall-ban  '109.248.9.9' 'SSH'
2018-04-09 14:15:21 v-delete-firewall-ban  '52.170.5.151' 'SSH'
2018-04-09 14:17:08 v-add-firewall-chain  'SSH'
2018-04-09 14:17:08 v-add-firewall-ban  '52.170.5.151' 'SSH'
2018-04-09 14:22:39 v-delete-firewall-ban  '109.248.9.9' 'SSH'
2018-04-09 14:27:08 v-delete-firewall-ban  '52.170.5.151' 'SSH'
2018-04-09 14:28:55 v-add-firewall-chain  'SSH'
2018-04-09 14:28:55 v-add-firewall-ban  '52.170.5.151' 'SSH'
2018-04-09 14:33:42 v-add-firewall-chain  'SSH'
2018-04-09 14:33:42 v-add-firewall-ban  '111.67.197.84' 'SSH'

[ScIT]

Also I enabled autoupdate and it seems like it happen after the latest version 0.98 release 22 ?

R22 was only a small security update inside of the api. So I think this is not related to the update: https://github.com/serghey-rodin/vesta/ ... 8fb0b23e9a

But no idea why this happens, can you check with another browser or with incognito mode?

[yoko eagle]

Tried everything on chrome latest version, nothing changed.
Problem solved after changing the browser to Firefox and clear cache.
Regard!