Bob Felts
Well-Known Member
It is easier when:Sorry Bob but I work for the world 2nd largest provider. Know several people that I work with/for that could create and correct the issues. I know of 3 other forums that have gone through similar issues, and those took days/weeks to fix, this has been months.
A. You actually own the server that you need to fix. When the server us owned by the ISP and they make their income from it, they may not give you root access and carte blanche. Not all (read that any) ISPs are willing to let you make any changes outside of your docroot or perhaps your own homedir.
B. You have the full workday to get fixing the problem. Not start to affect repairs at 10 PM after your workday is done, and the kids are fed and in bed.
C. You built the server in the first place and don't have to do discovery in the first place to understand what is on it, and how the server was built. Which version of header files were used for a build, etc. And can even take the entire server down for a reboot or restart a single service. Some ISPs are not helpful at all if your SW needs a different version of a package to support your app. They don't care if you are stuck. They will tell you to find forum SW (in this case) that does work with their stuff.
D. You are competent to work at this level. Whin I hear that someone wants to RTFM for the forum SW and fix things by goosing a config at the script level, I'm thinking I'm hearing from a neophyte script kiddie. If you have to recompile Apache Server SW to get virtual hosts to work, (an example only) you are totally beyond massaging the apache.conf files. You think a business will let someone renting domain space on their server will let them do this kind of thing? That's a load of crap.
E. Then there is the possibility that this is a matter of dragging of feet. Who knows besides the admins?
Sent from my SAMSUNG-SM-N910A using Tapatalk