/usr/local/hestia/bin/v-change-sys-port 8083
You probaly need to restart the hestia service after that.
done this:
root@xx:~# /usr/local/hestia/bin/v-change-sys-port 8083
root@xx:~# service hestia restart
and then i can login
THX
but i can change port to other number or i must have 8083 for ever ?
You probaly took a port which is used by another service. You can take every other port you want, which is free.
And well, user mistake, please stop to blame the update just because it restarts the hestia service…
that other port, which you say is an error, has been in use on 10 vps with hestiacp, for many months and all other updates have NEVER caused this problem. so I don’t think it’s my mistake!
rather it would be appropriate to remind users that in case of use of alternative ports to 8083 in case of major upgrade it is necessary to restore the default port 8083 because this wants it necessary!
Thats not needed at all. There are 12k servers updated, your servers which you probaly used the same port on every server started to fail - we still dont know which port you used, but its clearly in use, thats why hestia service was not able to restart. Why it was in use we cant say, also cant monitor - its your system. Setting it to 8083 just proofed that the other port was in use which we found out due to the error log - the from me written “basic debug”.
You can now go further, check the port you used before, validate which service it took it and why including when.
I confirm that the port I used for many months with hestiacp 1.4.17 now with version 1.5.1 is not free, in fact changing it with another number works correctly. You have probably changed the numbering of possible doors with the new version. I use different control panels both derived from vestacp and from other sources.
And hestiacp is one of those that has given less problems over time.
However, I am very happy with this panel, and the work you are doing is great. I understand that you might not believe me, but if it were only one vps to give problems I could also say that the error is mine or that of my vps provider, but when there are many panels that give the same error, things do not add up. I apologize if the tone has been altered, the main cause is my poor knowledge of the English language! Good job and see you next time
Do you want to share your used port? Have you found out, which service it took it?
To be exact we have changed:
Bugfixes
- Add B2 delete file support to BlackBlaze
- Open phpmyadmin in new tab or window #2250 @manuelserol
- Fix issue with ipset not working properly Forum
- Improve port detection on multiple servers for SSH #2242 and #2255
- Fixed an issue with # in config files
- Fixed multiple bugs in installer
- Set correct permission /install/deb/ folder
- Adjust /etc/apt/sources.list.d/hestia.list to include architecture to resolve issue with I386 missing in apt.hestiacp.com
- Fallback to hostname without retrying ptr lookup in exim (#2259)
- Enable quota with in dovecot when sieve is enabled @madito
- Unable to edit php8.1 service #2261
And we restarted all the services (as done already for ages)
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.