Search results

The permission of /conf/ is supposed to be 750 as below drwxr-x--- 5 lsadm nogroup 4096 Feb 25 02:02 conf/ You made change to 755 is to let others can read your conf. This may cause a security issue. This is why we will automatically fix this issue when you start the service. Can you try to...

I tested you case. ` -wplang en ` should be ` --wplang en `

OK. Thanks for posting.

I see it. You can do `.........lsws/bin/lswsctrl stop` and then you can `systemctl start lsws` or run /usr/local/lsws/admin/misc/lsup.sh -e 1.6.9

After you typed the command and press Enter, the script will notice you the whole settings in the first screen. Then you can choose continue or not.

Thank you for telling me that.

Please run again. /usr/local/lsws/admin/misc/lsup.sh -d -e 1.6.9 Your lsup.sh is too old, and newer version will continue to run after it update itself.

Can you tell us what do you mean `hangs all the time `? Can you explain in detail?

If you still have the IPv6 port occupied issue, can you try our new release 1.6.9? This fixed a restart issue. I want to know if it cover your case or not. Because I can not reproduce it. /usr/local/lsws/admin/misc/lsup.sh -d -e 1.6.9 Thanks David

Thank you for remind me. I will work on this issue in the next few days.

What is your errorlog settings?

Can you try new version 1.6.9 which just changed a little of the log setting? Run /usr/local/lsws/admin/misc/lsup.sh -d -e 1.6.9 Thanks David

OLS does not fully support the .htaccess. LSWS is 100% compatible with Apache configurations.

I am so sad to saw the bug is back. Yes, I made mistake to merge some big code changes and reviewed that diff one by one for 3 days, but may still miss some error. But the code changes did fix some hidden bugs. I will fix this issue soon. Please switch to 1.6.7 for now.

Yes, Just released.

Maybe a bug. Can you test 1.6.8? run lsup.sh -d -e 1.6.8 to do a quick upgrade.

You may upgrade to 1.6.7 or wait for a while and we will release 1.6.8 soon.

In detail? So what is the request and do you have the log?

Thank you for your info. David

You may raise a ticket so that our support team can help. I am sure 1.6.7 is tested before released.