Sudden problem accessing DA control panel and SSH..

Richard G said:
Well... that's a bit of a problem, because this is something which happens both with noobs and with professionals (as they know how things work and often are less patient or read less manuals). Like I said, also happened to me the first time. So I guess we can carefully say that is the root cause of the isseus encountered.
However most cPanel admins we see here... lets say the ones with a enough knowledge coming ove are scarce here. You're one of the few exceptions to this.
Indeed it's expectable that you're in a bit more haste and already pre-irritated coming from another debacle. Who wouldn't be.


Unfortunately that seems indeed the case. And things you installed manually then most likely only added to the problem. And makes it that at this moment there is no easy fix. Otherwise we might have be able to try a forced "build all d" and then resetting permissions and rewrite_confs and probably things would have been fine then. But I doubt that will work now.
And since there are manually additions/installations done, I won't try to advise it because it might mess things up more and I don't want you to get more trouble as you already have.


Only syslog and ssh log maybe. Because those are the logs you find in the csf.conf file. The list too look at is indeed the syslog (if you're on debian) but also logs present in the /var/log/directadmin directory, which also state what happens on login attempts and issues. Various logs in there.
Probably they will contain loads of errors because the initial install already wasn't good enough.


I most certainly agree with you here! It's said that you can start configuring then already. But it's prooven that this won't work. Yes you can set some basic settings for DA itself already but not really start like one would expect.
It would at least be good to issue a very clear warning to limit all actions to only DA related settings until installation is totally complete.

For the rest... well... DA is cheap and works great but needs some more attention. But well... as with all things. Price differences have reasons.

I'm sure if you would start over with DA, now knowing you have to wait, and it's not everything click and play like cPanel, you would appreciate what you get for the price, as do thousends of others, also big firms and people with kindlike knowledge.
It's a choice.
Click to expand...
Now that you mention it, I am just remembering the tech guy gave me a very dry explanation as to why the domains failed to properly create and it was along the lines of a permissions problem I believe.

My problem right now is to determine what is failing, to re-install or any sort of general inspection and correction of problems I believe will take a similar amount of efforts and time as a complete migration to CPanel. I do have the main domain and all domains in that server controlled by a DNS service so I can point them to a secondary small server if needed (proliferating in seconds), but the capacity of that one is very limited and if google detects a problem with loads it stops crawling and then penalizes me, it has happened that just when I am servicing stuff my bad luck sends Google bots my way when my pages are super slow, and then suddenly I start going backwards with indexing and my keywords start disappearing.

It took me about 2 years to finally get indexed for hundreds of pages and the goal was to index first 3 thousand pages then 50 thousand then 250 thousand then over a million (this is a huge project). Getting properly indexed and positions with CMS sites is so difficult...

The whole purpose of that server and project was to move away from Apache and achieve Litespeed grade scores in Lighthouse, and I did... finally I am beginning to get great scores and good SERPS. With that DirectAdmin install, it is just that every once in a while like this week the gremlins just pop...

As I said, babysitting a webserver control panel is not my job, it is basically one piece of a one thousand piece puzzle and I can't keep having problems with that small piece... But it so happens that piece is a foundational piece of the whole thing. Never in like 27 years doing this had I had a spell where all the web server panels I tested all were super unstable and causing major issues, but at least DirectAdmin has never collapsed the site, Cyberpanel did twice with their messed up caching system...

It is my fault for being cheap, I wanted to stick it to Cpanel for increasing their prices so dramatically but in the end I just screwed myself..

I see why CPanel's people think their product is so pricey, now I understand.. People like me , we just got used for many years to not pay them what they are worth and now they are collecting and it is sort of fair. I have a similar problem with adobe and licenses, we used to get a license for the whole software package, now they price it based on individual users and yearly, it became a massive yearly bill but the product is sort of worth it I guess.

This is a dilemma, on one hand I think I went though most of the learning curve of DirectAdmin and am almost there, I have all the plugins and modules working, I have great speed and google efforts are beginning to pay off, we moved recently the management section of the server to a local network and connect it now via VPN and added and are still adding security layers to sort of keep the attacks at bay, but on the other hand I hate when suddenly my life goes upside down for no reason, especially with something as dramatic as not having access to my panel or SSH. We did a lot of work setting up several security levels on that server, suddenly one of them (the change of ports) just blew up in my face for no reason apparently (I guess the reason is your theory about the background install processes getting corrupted).

I am going to do a little more research to find a reasonable explanation and at some point decide what happens with that server. I am sure eventually I will go to CPanel and try to run Litespeed in it.
 
Last edited:
JGSFla said:
nd it was along the lines of a permissions problem I believe.
Click to expand...
Which can also very well (even most likely) be caused because a too early creation when background was still running.

In case you still want to try to see if basic things would get fixed, this is an option, but again, very much at your own risk. Normally it wouldn't heart, but seen you did some manual installations, one never knows.

Code: 
cd /usr/local/directadmin/scripts
./set_permissions.sh all
da build update
da build all
da build rewrite_confs

It might work, it might not. At least it will rebuild everything which was done in the beginning, without changing any configs and there is a chance things which were not taken in effect before will be picked up now.
 
Richard G said:
Which can also very well (even most likely) be caused because a too early creation when background was still running.

In case you still want to try to see if basic things would get fixed, this is an option, but again, very much at your own risk. Normally it wouldn't heart, but seen you did some manual installations, one never knows.

Code: 
cd /usr/local/directadmin/scripts
./set_permissions.sh all
da build update
da build all
da build rewrite_confs

It might work, it might not. At least it will rebuild everything which was done in the beginning, without changing any configs and there is a chance things which were not taken in effect before will be picked up now.
Click to expand...
Thanks so much, I think if I create an entire backup of the server so at least I have a way to revert back to the current state that mostly works I can try what you suggest at no risk and do it one night in the middle of the night.
 
JGSFla said:
As far as the other comments, lots of smartasses in these places as usual. I am a programmer in 4 computer languages, I have developed over one thousand large and complex websites hundreds of CMS ones, developing lots of my own programmatic solutions (no plugins).
Click to expand...
Yet, can't get to grips with a new control panel..... Seriously, if it was a critical server, you would known to set up a test server beforehand (I know you do colocation but) - that way, if things went belly up, you could've known why if it happens on the "real" server.

Just my 2p's worth.

NB. I consider myself a smart@rse too.
 
The way you talk here and show that you are so smart through a high IQ test already gives me the feeling that you don't know what you are doing. Perhaps @zEitEr can help if you create a ticket with him and grant access.
 
You must log in or register to reply here.
Back
Top