- General
-
Questions
0
Answered
Cannot log into ajenti after digitalocean droplet resize
Was running on my DigitalOcean VPS with only 1gb of ram. did a droplet resize to get to 2gb. nothing else changed other than processor and ram size. same domains same IP same everything, however now going to my webnetvn.com:8000 brings me to connection attempt to
checked ajenti's configs and everything looks right still. somewhere i might be able to check figure out why this is happening?
Thanks in advance.
| webnetvn.com was rejected. The website may be down, or your network may not be properly configured. |
Thanks in advance.
Answer
0
Answer
Answered
Eugene Pankov (Project coordinator) 10 years ago
Panel opens up just fine at https://webnetvn.com:8000/
Bump!
is there somewhere i can go for paid support i need this sorted ASAP, as it seems other systems are also having problems IE mail and i would like to get into ajenti to figure out whats happening there! i would be perfectly fine doing the support myself but i cannot seem to find anything that could be causing the issue, if someone could just point me in the right direction please?
is there somewhere i can go for paid support i need this sorted ASAP, as it seems other systems are also having problems IE mail and i would like to get into ajenti to figure out whats happening there! i would be perfectly fine doing the support myself but i cannot seem to find anything that could be causing the issue, if someone could just point me in the right direction please?
never mind, i got it sorted for some reason after working for a few weeks with the hostname set as the server's fqdn, it no longer wanted that after the upgrade, i now needed to use the server's ip.
Answer
Answered
Panel opens up just fine at https://webnetvn.com:8000/
right. i mentioned that i got it working. is it required that the hostname be set to the ip and not the fqdn?
No, it's not required, e.g.: https://104.236.18.21:8000/
righ tif i change the hostname in the panel to vn137.webnetvn.com the panel no longer works (which was the issue here even though the panel worked fine on this configuration previously)
)
)
I'd speculate that you have an /etc/hosts entry which maps vn137.webnetvn.com to a non-public IP.
Customer support service by UserEcho
