Unreachable DA Login @ Unexpected updates trouble

Achterstraat

Achterstraat

Verified User
Joined
Mar 21, 2015
Messages
79
Location
Netherlands
Last weeks there are some troubles with DA updates, don't say anything about that but again updated without permissions with the follow result;

1673209332683.png

1673209347236.png

1673209360184.png


Yes, all update channels (current/stable/alpha) give errors on just a skin.. ..no access to directadmin, how to solve.. ..trough these autoupdates/hotfixes different websites are also unavailable!


What's happaning tonight around 3 o'clock?

1673209412406.png
 
Last edited:
Before christmas current channel, once switched to alpha but back to current last thursday.

For all domains i use login.domain.tld to redirect to login.domain.tld:82 for the DA login, root.domain.tld is the hostname where i can login by root.domain.tld:82 and of course directly on 127.0.0.1:82 but not anymore on login.domain.tld:82, see errors in previous post!
 
hi everyone, DA would not jump between alpha/current/stable releases on its own.

Skin problem might be caused by using too restrictive feature sets. If a feature set for core_function only were copied long time ago it might no longer work with modern Evolution because it requires access to new endpoints. Anyone using built-in feature sets got updates, but making a copy and keeping it might lead to such situation.

@Achterstraat are you using feature sets?

Code: 
$ grep -rn feature_sets= /usr/local/directadmin/data/users/

It would be best if you would open a support ticket and give us SSH access to the server to investigate it further.
 
Mine was in stable, still same happened with 2 installation.
Any hotfix available for now?
 
To fix it we first need to understand the root cause for this. This is definitely not a wide-spread issue. It was a guess regarding the feature sets. Would be great to get access to a system affected by this so we could understand the root cause.
 
fln said:
To fix it we first need to understand the root cause for this. This is definitely not a wide-spread issue. It was a guess regarding the feature sets. Would be great to get access to a system affected by this so we could understand the root cause.
Click to expand...
There are about 500 account on that server, is it safe to provide access ? should I open a ticket?
 
Yes - it is safe. Please create a support ticket, once we have support ticket we could safely request access without disclosing any info about the server publicly.
 
We just got access to @Ranjan server but there were no issues. When we connected everything was already working fine.

We have not changed anything. I think the problem was solved automatically with DA hot-fix. If anyone still having this problem and have auto updates disabled latest version can be installed from CLI with command:

Code: 
/usr/local/directadmin/directadmin update
 
This morning everything was working fine after changing back to current, nothing changed and 12 hours later the same problem, again.. ..not only login.domain.tld:82 but also unable to login by root.domain.tld:82 or ip:82

I'll open a support ticket, adding or changing cronjobs also not working anymore trough DA GUI, only manually changes by SSH, same with PHP Selector for versions..

See ticket #46009 for details.

Update: If i change ServerName in /etc/httpd/conf/ips.conf to for example directadmin.best.software than i can use that domain on the port in directadmin.conf given, non other domains (or ports lol). So, if i fill in root.domain.tld it's working for root.domain.tld, before also other domains are working on port 82. But. cause updates overwrite ips.conf to shared.domain, i have to change it before i can login (or have to add shared.domain to local hosts file, but that's only working on 1 machine.
 
Last edited:
You must log in or register to reply here.
Back
Top