• There is NO official Otland's Discord server and NO official Otland's server list. The Otland's Staff does not manage any Discord server or server list. Moderators or administrator of any Discord server or server lists have NO connection to the Otland's Staff. Do not get scammed!

MyACC - Cannot find config.lua file. Ubunu 22.04

drewny

Member
Joined
Sep 3, 2021
Messages
21
Reaction score
24
hi
Ubuntu 22.04 here (fresh install)
I copied MyACC files to /var/www/ots/
i configured virtualhost

<VirtualHost *:80>



ServerAdmin [email protected]
ServerName domain.com
ServerAlias www.domain.com
DocumentRoot /var/www/ots



ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined


</VirtualHost>

i set
Code:
sudo chown -R www-data.www-data /var/www/*
sudo chmod -R 760 system/cache

my dir with tfs /home/ddd/Desktop/OTS/forgottenserver-1.4.2

Basic configuration​

Server path
get error --> Cannot find config.lua file. Is your server path correct? Go back and check again.


any hint?
Apache don't send any error
 
Give config.lua, 777 chmod. Thats the current workaround. The proper solution would be changing apache2/nginx running user to same user you use for otserv, like otsmanager or your user. But the 777 chmod works, and is easy to apply, so why should we care. The problem would be only on multi-user machine, where everyone can read your config.lua, but most servers are hosted by 1 user, and not shared with anyone.

chmod 777 config.lua

Then, for all directories that are before config.lua path, add execute bit (+x)

chmod +x /home
chmod +x /home/ddd
chmod +x /home/ddd/Desktop

etc.
 
Why not simply add it to group www-data so it can read/write/execute within group
chown -R www-data:www-data config.lua
chmod -R 660 config.lua
We only need to read these files I guess.
Never tried that but maybe it works :)

Edit:
I’d try with adding users to some group with:
- usermod -a -G
And not changing owner of file but maybe only group
- chgrp -R
 
Last edited:
Give config.lua, 777 chmod. Thats the current workaround. The proper solution would be changing apache2/nginx running user to same user you use for otserv, like otsmanager or your user. But the 777 chmod works, and is easy to apply, so why should we care. The problem would be only on multi-user machine, where everyone can read your config.lua, but most servers are hosted by 1 user, and not shared with anyone.

chmod 777 config.lua

Then, for all directories that are before config.lua path, add execute bit (+x)

chmod +x /home
chmod +x /home/ddd
chmod +x /home/ddd/Desktop

etc.
it's safe to give +x on home dir?
 
it's safe to give +x on home dir?

If you are the only user running on the machine, then yes, its safe.

In other cases I am not really sure. It will be possible for other user to enter the folder, but it won't be possible to list the files inside, so yes its safe too.
 
Back
Top