Asura

Hi WillSuranol, JoWei is correct; but you must also remember to compile under Linux and then run 'athena-start' as JoWei stated.

Hi lunawany88, You must put the correct subnet; subnet: 255.0.0.0:127.0.0.1:127.0.0.1 Also, make sure you have portforward the ports 6900, 6121, and 5121 for the router. If you need help in portforwarding these ports for your router model, I would suggest reviewing this site: http://portforward.com/

Hi lunawany88, The issue you are facing is a mis-configured *_athena.conf files. Within the 'char_athena.conf' and 'map_athena.conf', make sure you are using the WAN IP and no '127.0.0.1' for the 'char_ip', 'map_ip', and 'login_ip'. From what I am seeing from your first post, the correct WAN IP is '60.54.40.44'.

Hi biohazard0134, As darristan stated, you need to use a service like NO-IP. I would suggest that you go to the following site for more information; http://www.no-ip.com/

Hi Butch, Within your FluxCP folder, look for a file named 'error_log'. Open that file and see what file it is reporting to have an error; I believe that within the custom theme files, there might be a file which you need to declare the MySQL information.

Hi xiaofu, Please go to this site; http://whatismyip.com Then use this IP to replace all the 'login_ip', 'char_ip', and 'map_ip' values. After this is done; make sure that you have the port correctly forwarded for your home computer. If you have not done this yet, you may go to this following site to find out how to do this for your router; http://portforward.com/

Hi x0ep, What happens when you attempt to run 1 of the servers individually? Try... ./login-server_sql

Hi xiaofu, What IPs did you set in your char_athena/map_athena files within the conf folder? It may be that the IP being used is incorrect so it cancels out your connection between the login and char server.

Hi WillSuranol, You are actually suppose to type, 'gdb ./map-server_sql'. map-server_sql will open in GDB within the terminal, and then you must type 'run' to start the debugging process. After it receives the crash signal, you will type 'bt full' to get the report.

Hi WillSuranol, CSF can not protect well against true DDOS attacks, however, it does well against small DOS attacks. I would suggest to see if your VPS provider has enabled the IPTables modules for your service first... if not, setting CONNLIMIT and PORTFLOOD is absolutely useless since it can not track any of the connections properly... cd /etc/csf ./csftest.pl If it works, then I would recommend reading this over: http://configserver.com/free/csf/readme.txt

Hi rkhin28, You can easily use any program that has SFTP such as WinSCP or FileZilla and the connect to your server to transfer the files over. After transferring the files, simply compile the server within CentOS and configure the conf files to have the correct information; after that you should be able to run the server within CentOS with no issues.

Hi Automatix, You can add me on Skype (Kopono); we can definitely work something out.

Hi jordan, You need to enter the correct information within '/config/servers.php' of your FluxCP directory. At the moment, it is configured to connect to '127.0.0.1'; it should be your own home computer's IP instead (since this is where you are hosting your RO Database).

Hi leadtech, The correct syntax should be this... CREATE TABLE IF NOT EXISTS `mainnews` ( `post_id` INT(11) NOT NULL auto_increment, `title` VARCHAR(60) NOT NULL, `message` TEXT NOT NULL, `poster` TEXT NOT NULL, `date` VARCHAR(255) NOT NULL, PRIMARY KEY (`post_id`), ENGINE=MyISAM AUTO_INCREMENT=0;

Hi Mentalist, Keops provided a good reminder; rAthena does not allow you to have s1 / p1 as the username and password combo for the server. You MUST change it in order for rAthena to work.

Hi mitsukee, You would need to import the .sql file to your "rathena" database. You can find the .sql here: https://github.com/calciumkid/fluxcp-renewal/tree/master/data/schemas/logindb If you don't know which, here are the specifics... 1) https://github.com/calciumkid/fluxcp-renewal/blob/master/data/schemas/logindb/cp_credits.497.sql 2) https://github.com/calciumkid/fluxcp-renewal/blob/master/data/schemas/logindb/cp_credits.743.sql If you are missing any other tables, it should be pretty obvious which to import back to your "rathena" database.

Hi mitsukee, There you have it; it is missing a table. Table 'rathena.cp_credits' doesn't exist

Hi jordan, You need to edit the '/config/servers.php' file inside your FluxCP, and put the correct MySQL information. Since you are hosting the MySQL information on your own PC, you must use your PC's IP (whatismyip.com) instead of 'localhost'. And you must port forward (portforward.com) 3306 for your PC in order to allow your webhost to connect to your MySQL server.

Hi mitsukee, Turn on error reporting by editing the '/config/error.php' file inside your FluxCP directory. Then switch false to true for the error_reporting value; after this is done, retry to log in and it should show a more detailed error message. Post it here so we can see what the real issue is.

Hi jordan, I would suggest turning error reporting on so that we can better investigate the issue. You will need to edit '/config/error.php', and then turn error_reporting to true. When you revisit the site, it should have a more detailed explanation on what the issue is.

Hi mitsukee, You can just edit the '/config/servers.php' to link your FluxCP to the proper MySQL database.

Hi poter21, I would recommend that you consult your provider and ask them to set ACL's on their network router to prevent UDP to all ports besides the ones that you truly need; this is the best method in preventing your port from being hogged by the attack. On your server, you may use IPTables to block out all the attacks that you don't want. Here is a basic IPTables script for you; #!/bin/sh # Clear all settings /sbin/iptables -F /sbin/iptables -X /sbin/iptables -t nat -F /sbin/iptables -t nat -X /sbin/iptables -t mangle -F /sbin/iptables -t mangle -X /sbin/iptables -P INPUT ACCEPT /sbin/iptables -P FORWARD ACCEPT /sbin/iptables -P OUTPUT ACCEPT # Allow unlimited traffic on the loopback interface /sbin/iptables -A INPUT -i lo -j ACCEPT /sbin/iptables -A OUTPUT -o lo -j ACCEPT # Set default policies /sbin/iptables --policy INPUT DROP /sbin/iptables --policy OUTPUT DROP /sbin/iptables --policy FORWARD DROP # Allow unlimited input/output traffic /sbin/iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT /sbin/iptables -A OUTPUT -m state --state NEW,ESTABLISHED,RELATED -j ACCEPT # Set SYNFLOOD inspection chain /sbin/iptables -N AH_SYNFLOOD /sbin/iptables -A AH_SYNFLOOD -f -j DROP /sbin/iptables -A AH_SYNFLOOD -p tcp ! --syn -m state --state NEW -j DROP /sbin/iptables -A AH_SYNFLOOD -p tcp --tcp-flags ALL ALL -j DROP /sbin/iptables -A AH_SYNFLOOD -p tcp --tcp-flags ALL NONE -j DROP /sbin/iptables -A AH_SYNFLOOD -p tcp --tcp-flags ACK,FIN FIN -j DROP /sbin/iptables -A AH_SYNFLOOD -p tcp --tcp-flags ALL FIN,URG,PSH -j DROP /sbin/iptables -A AH_SYNFLOOD -p tcp --tcp-flags ACK,PSH PSH -j DROP /sbin/iptables -A AH_SYNFLOOD -p tcp --tcp-flags ACK,URG URG -j DROP /sbin/iptables -A AH_SYNFLOOD -p tcp --tcp-flags FIN,RST FIN,RST -j DROP /sbin/iptables -A AH_SYNFLOOD -p tcp --tcp-flags SYN,FIN SYN,FIN -j DROP /sbin/iptables -A AH_SYNFLOOD -p tcp --tcp-flags ALL SYN,RST,ACK,FIN,URG -j DROP /sbin/iptables -A AH_SYNFLOOD -p tcp --tcp-flags SYN,RST SYN,RST -j DROP /sbin/iptables -A AH_SYNFLOOD -p tcp -j ACCEPT # Allow incoming TCP port 22 (ssh) traffic /sbin/iptables -A INPUT -p tcp --dport 22 -m state --state NEW -j AH_SYNFLOOD # Allow Ragnarok Online (TCP) /sbin/iptables -A INPUT -p tcp --dport 6900 -m state --state NEW -j AH_SYNFLOOD /sbin/iptables -A INPUT -p tcp --dport 6121 -m state --state NEW -j AH_SYNFLOOD /sbin/iptables -A INPUT -p tcp --dport 5121 -m state --state NEW -j AH_SYNFLOOD # Allow MySQL /sbin/iptables -A INPUT -p tcp --dport 3306 -m state --state NEW -j AH_SYNFLOOD Please note that this is a static rule for generally blocking out basic attacks. It would be more recommended if you use a more dynamic and active firewall such as CSF or APF; these may proactively protect you from DOS attacks. After installing CSF or APF (your choice); you need to adjust a lot of settings to enable/disable different functions. And then you should install (D)DOS Deflate; http://deflate.medialayer.com/ If you have done all this and still suffer from attacks; contact your host to fix their 'sysctl.conf'. A lot of spoofed attacks and martian packets can be dropped at the server level before it reaches to your VPS; so it'd be their responsibility to make sure that it's properly configured to do this. Good luck with your issue!

Hi wiideliva, Try after making that change for your MD5 value; you must clear your cache files inside '/data/tmp' within your FluxCP directory. Inside that 'tmp' folder, you must delete all the *.php files. (They will be re-generated by FluxCP once you visit the site again.) You must also note that the accounts that you made BEFORE you changed the MD5 value, can not be used since it is assigned the MD5 hash instead of plain text. So you must re-register, and use the new account to log in.

Hi mitsukee, Using a webhost's MySQL server is not a good choice to host your RO database; especially for cPanel-based Webhosts. The cPanel-based Webhost has a MySQL configuration which is optimized and configured just for web hosting; short-lived connections and fast transactions. For hosting a game database, you'd need to have a MySQL server with a long keep alive timeout, along with the standard configuration for values such as 'key/read/sort buffer size', 'max allowed packet', 'thread stack', 'cache', and more. So you'd be better off if you just installed MySQL on your computer and used that SQL server to host your RO database instead.

Hi Mentalist, If you are just trying to run a test server and not allow outside connections, then you would use '127.0.0.1' as jordan stated. And if you correctly portforwarded your ports for your LAN IP, it should have worked just fine. I'd recommend checking if you have the correct WAN IP set in your conf files; most Internet Service Providers provide you with a dynamic IP, meaning it changes every 12/24hrs.