Search results

Upgraded to centos 6.6 today, and I'm on OLS version 1.3.5 and it seems the admin listener port was reset to the default 7080? Not sure if that is normal or not.

Not sure if it's the same issue, but after I upgraded to the newest version it wasn't working at all. None of my web pages were loading, not the admin control panel either even though litespeed was still running. Didn't see any relevant errors in the error log, downgraded and it was working again.

Oops, my fault... :oops: I forgot the port to access the CP so I googled it quickly and saw 8088. Of course that was just the default port for web pages when you first install OLS and not the CP port, which is 7080. I knew 8088 didn't seem right, but well it happens when you don't use things for...

I upgraded my virtualbox test installation to 6.5 and I'm not able to access the litespeed control panel. It doesn't load as if the page doesn't exist, I tried with both http and https. Any one else have this issue? Although I haven't tried to visit the CP on this installation in a while, so I'm...

Did you try with a beginning forward slash? I forget, but I think it may be required.

I did this before and it was pretty easy. I think the example comes with one set up. Did you try following that and just changing what needs to be changed?

That's good to hear. As for the grammar, I wasn't necessarily correcting my own mistake, rather asking for confirmation as I still manage to mess that up often enough. :oops:

I think I can take your word for it then, but if it's easy to check I wouldn't mind. :P I figured when receiving bug reports for litespeed devs might also take a look if the issue exists on the open version, but maybe the code is a lot different and this doesn't happen. BTW, anyone want to help...

Just wanted to double check that this does not effect openlitespeed: http://www.webhostingtalk.com/showthread.php?t=1318008 Thanks.

Haha I noticed that the first day... IIRC I saw nginx. I'm guessing he was just hosting it on server he already had other sites on.

Are you asking if it works with that? If so, I'm using 64 bit without issues.

This thread must be a cover up. In other words, you must use this option, "Yes, but I'll tell everyone that I don't have access to the Internet." It's exactly that... Just kidding. :P Do you regularly visit Japan? I would really like to go there one day... Have a great vacation! :cool:

This definitely makes upgrading a lot easier. If I already have OLS source compiled and now want to use yum, after adding the rpm am I able to simply do yum install openlitespeed to have it upgraded? Or are there different steps I should take for this case?

Managed to get it working. I didn't notice my rewrite rule was (.*), using ^(.*)$ worked, although I didn't think it would make a difference in this case. The weird thing is on one install using (.*) works... I'm just happy it works now. :)

Is there a special way to redirect the site ip address to the domain? I've tried adding to the rewrite section: RewriteCond %{HTTP_HOST} ^121\.121\.11\.121 RewriteRule ^(.*)$ http://my-domain.com/$1 [R=301,L] Also tried using: RewriteCond %{HTTP_HOST} !^www\.my-domain\.com$ RewriteRule ^(.*)$...

I forgot to post this last time, but I've run into this issue a few times now. Each time I upgrade to a new version my admin user is reset back to the default admin credentials, which is pretty bad security wise. It might have to do with my changing the user though. Instead of "admin" I changed...

Alright, good to know, I thought it was something wrong on my side or settings not used correctly.

Okay so I reset most settings to default and it failed, then instead of setting CPU limit, I set the max dynamic response body size to around 200M to test a 150M~ file and it's working now. (y)

Forgot to say, maybe there should be a note somewhere that they are for CGI processes only so that generally most people wouldn't have to adjust them much?

In my litespeed error logs I see a lot of error messages such as: 2013-07-25 14:08:03.644 [NOTICE] [IP:PORT] [STDERR] I think there should be a description of the error at the end of the line. Then I realized that in my php.ini I did not set my error_reporting, after setting to E^ALL I can see...