Internal Server Error on Install

[CyberShadow]

I have the latest version of SMF installed on an upgraded web hosting package. I am finding that some things are working fine, but it feels like there is an issue with permissions somewhere. For example, I have been able to install the ADK Blog package fine, but when I attempt to install the ADK Gallery package, I get an Internal Server Error.

This error is one that has come up several times in various places. If I could find a pattern, it is that files that I upload via FTP work, but files uploaded via the boards don't..... until I got ADK Blogs working!

[redone]

Check your server error logs for the actual message. Contacting your host is another step in the right direction. Could well be a hosting issue.

[CyberShadow]

Hi. Thanks for your response. The error logs show a lot of:

Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.

Is that related? Even if not, it looks like something I should deal with.... somehow.

The site is on VPS, which means that the host doesn't want to get involved and really makes me the web host.... meaning, yes, it is most likely a problem with a bad host! 

EDIT - Another symptom.... It seems like I am the only person who can post attachments to my board! Everyone else gets an error...

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, [email protected] and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

This confuses me.

EDIT2 - Update, apparently other members can attach PDF files but not images.... are they stored in a different place? Weirderer and weirderer.

[redone]

If you have a VPS and are not sure how to resolve the issues, then a shared host or someone to manage your box would be better. Again, before you can even troubleshoot you need the server error logs either way.

Those messages you are posting are just general SMF generated error messages. The logs will tell more. This one might have to be moved to the server config board as I doubt SMF is the culprit of your problems here.

[Colin]

+1 -- file permissions also may be the culprit here.

[CyberShadow]

Thanks guys. One of the reasons for moving to VPS - aside from the fact that the site required it - was to learn about this kind of stuff. The site is a hobby site, doesnt generate a real income and isn't critical, so I can't really afford a web support guy, and I am happy to learn it myself. It's interesting.

I guess that my next step is to double-check my file permissions - I am sure that I have done this, but I have learned that it is better to triple check than look like a fool! Following that, I will drop into the server config board, as it is looking more and more like this is the root of the problems. (root! Ha... I made a server techy joke!)

[MrPhil]

One of the reasons for moving to VPS - aside from the fact that the site required it -

Really? Unless you have a very large forum, or choose to use certain mods that really suck up CPU cycles, SMF rarely requires going to an expensive VPS. More likely you had some minor performance problem that could have been easily fixed, but a greedy or lazy host merely upsold you on a more expensive system.

was to learn about this kind of stuff. The site is a hobby site, doesnt generate a real income and isn't critical, so I can't really afford a web support guy, and I am happy to learn it myself. It's interesting.

As a hobby site, it would be unusual to demand so much processing power that you had to go VPS. If you need some income to help support the expense, think about running some ads.

I guess that my next step is to double-check my file permissions - I am sure that I have done this, but I have learned that it is better to triple check than look like a fool! Following that, I will drop into the server config board, as it is looking more and more like this is the root of the problems. (root! Ha... I made a server techy joke!)

Did you upgrade SMF and upgrade the server at the same time? That's usually not a good thing to do. It makes it hard to determine which action (SMF or server) caused your problems.

files that I upload via FTP work, but files uploaded via the boards don't

Usually that means an incorrect file transfer mode (binary instead of ASCII, or vice-versa). Did the files uploaded "via the boards" actually show up? Did they have content? Did it appear to be correct (lines not run together or line-ends not doing strange things)? I've heard of that problem happening with FTP, but not with SMF. What do you mean by "uploaded via the boards"? Do you mean that SMF did a package upload (of a mod package)? For SMF uploads, the problem is commonly directories that are not writable by PHP (which SMF is running on). If PHP is not running as the "owner", 755 permissions on directories will block uploading files. You should be told in the error message(s) which director(ies) SMF was unable to write to. You would change their permissions to 775 as a first try, and to 777 as a last resort.

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

That can be caused by many things. I give a checklist in my signature > FAQs > Internal Server Errors. You should read it, to at least eliminate the more common problems.

Unfortunately, it sounds to me like you have nowhere near the skill set needed to administer a VPS.

[CyberShadow]

Really? Unless you have a very large forum, or choose to use certain mods that really suck up CPU cycles, SMF rarely requires going to an expensive VPS. More likely you had some minor performance problem that could have been easily fixed, but a greedy or lazy host merely upsold you on a more expensive system.

Well, SMF isn't the only thing that I was running. I also use phpbb and Drupal, and wanted to split the site. The three factors were all putting too much strain on the database and causing issues with connections. It just made more sense to run VPS and split the site to maximise the available resources, rather than pay two hosting packages and continue shared database resources.

But, yes, my host wasn't the most accomodating in the world and I had my site locked a couple of times. I do think that part of it was them wanting to steer me towards a more expensive package... so when I upgraded I didnt go with them.

As a hobby site, it would be unusual to demand so much processing power that you had to go VPS. If you need some income to help support the expense, think about running some ads.

Yeah, that's the next step.... Anyway, I have a couple of IT friends who would take a look at it for the cost of a beer or two, but I am a believer in having a go myself and learning first hand.

Did you upgrade SMF and upgrade the server at the same time? That's usually not a good thing to do. It makes it hard to determine which action (SMF or server) caused your problems.

Nope. SMF is the same version. I always kept the boards up to date. I also keep a log of what I install and add to the site and boards as I go along.

Usually that means an incorrect file transfer mode (binary instead of ASCII, or vice-versa). Did the files uploaded "via the boards" actually show up? Did they have content? Did it appear to be correct (lines not run together or line-ends not doing strange things)? I've heard of that problem happening with FTP, but not with SMF. What do you mean by "uploaded via the boards"? Do you mean that SMF did a package upload (of a mod package)? For SMF uploads, the problem is commonly directories that are not writable by PHP (which SMF is running on). If PHP is not running as the "owner", 755 permissions on directories will block uploading files. You should be told in the error message(s) which director(ies) SMF was unable to write to. You would change their permissions to 775 as a first try, and to 777 as a last resort.

The packages upload to SMF fine, but its on the install package stage that the server error turns up. No other errors or obvious problems aside until the server error hit. The only error message was the internal server error page. All directories are 755. That was my first thought too.

That can be caused by many things. I give a checklist in my signature > FAQs > Internal Server Errors. You should read it, to at least eliminate the more common problems.

Unfortunately, it sounds to me like you have nowhere near the skill set needed to administer a VPS.

Many thanks. I will head off and read the list in your sig.

So far, I have set up my server and accounts, transferred all data from the old host, installed the platforms required and got everything working aside from a couple of packages that won't upgrade. For a noob, I think I am doing OK, and this is really the only issue that I am having with the entire transfer and server upgrade.

I think that it's really a matter of experience more than anything else, and that's what I am going for here. I have learned a lot over the years of running a site on shared hosting, stuff that I would never have got around to otherwise. Once I get this sorted out, I am sure I will be fine for the short term future.

Thanks.

[CyberShadow]

Just to update, but I think that I have solved this. I was also having a problem elsewhere, which turned out to be the FcgiMaxRequestLen set too low by default. I have yet to test the increased limit with regards to installing packages, but I expect this to have been the same source of the problems and so should now be done.