Asura

Hi Yoona, Definitely not even close... the login port should be the only thing of concern.

Thanks Asura it worked, finally! Hi Z e r o, Yeah, not a problem. @Kenpachi - "you answer is completely pointless. Maybe you should think about your hosting service if you don't know the basics of computer systems. (I know, I sound harsh but it's the truth.)" Completely pointless? Doubt it. Truth about what again? LOL.

Hi curiosity, Why not host a demo so that we can all test? If you need a VPS, feel free to let us know; we'd be more than happy to sponsor another cool project. Thanks for your kind offer. Maki has also offered access to a VPS, so it looks like I'm good for now. I'll make sure to upload something everyone can try out soon. GitHub is also updated, for those who are interested. Hi curiosity, Sounds great, very much looking forward to it!

After setting up your MySQL server you have to create a user which is used by the RO server to communicate with the MySQL server. The account you created must have the proper privileges for your RO database to be able to select, edit and delete data. Most common way for newbie is to use the option "create database with same name and grant all privileges" (or something similar) when creating the user for the MySQL server. If you do so, you wont have to set up the privileges on your own. make sure you changes it in the config files and also in the "login" table of your database. If your phpMyAdmin is accessable through 127.0.0.1 it's on the local computer. Hi Kenpachi, Really? I believe I know what I am talking about. Please Z e r o, confirm my answer has worked for you; because it's been known to resolve issues in regards to this in the past. Your hostile attitude is irritable to people whom are here to help others, I would prefer you retract that statement. There is a difference the way 127.0.0.1 and localhost is handled, because of how it involves the IPv4 and IPv6 addresses. Also... I think for someone with an issue whom is hosted with AsuraHosting, the guys at AsuraHosting would be the best people to ask for resolution to the issue...

Hi Z e r o, It's simple; just edit your '/conf/inter_athena.conf' and change the "127.0.0.1" values to "localhost". Save and run; it should work just fine.

Hi Yoona, Check if your GRFs being used, has a clientxml.info file which is incorrect. That is most likely the reason for your issue.

Hi senpuuki, From what I know; there's a setting within the conf which you have to properly declare the log file names... I forget which. But I recommend, as a quick fix solution to your problem; simply grab the eAthena's "athena-start" file. cd /location/to/your/emulator rm -rf athena-start wget http://eathena-project.googlecode.com/svn/trunk/athena-start chmod +x athena-start After this, you should be able to run the "athena-start" file just fine.

Hi lipitb, I am not sure if this will work 100%; but for your char_ip/login_ip/map_ip in the '/conf' folder, change it to your hostname from No-IP (ragnahome.servegame.com). It *should* work when your IP resets as the No-IP application would update your hostname with your new IP.

Hi Yoona, 3306 isn't required to be opened unless you are hosting your website elsewhere (other than the same place you host your RO server). As for your multiple GRF issue; make sure that you do not have faulty clientinfo.xml within the GRF which may lead your client to connect to the wrong service.

Hi panducakep, I would suggest that you check your PHP modules, make sure that mcrypt is installed properly. Otherwise, a quick fix would be to disable recaptcha in /config/application.php.

Hi rakuzas, I would suggest that you change your host. MySQL 4 is pretty much deprecated. The past few years (5+ years?), people have been using MySQL 5 and more recently 5.5. Otherwise, if you are happy with your host; demand them to change it for you. As for your login issue; make sure that your FluxCP is installed in the same database as your Athena emulator's. This is a requirement.

Hi kangfredy, What is the OS bit? 32 or 64? If you have a 64bit OS, you have to ./configure with the enable 64bit flag. ./configure --enable-64bit make clean make sql @funtwocrasher - How does RO .SQL have an effect on compile errors? You must be pretending to help.

Hi P r o p e r t i e s, It says how to fix the issue here; "Remedy with `chmod 0600 /usr/html/cp/data/logs`" So you have to type the following in SSH/Terminal. chmod 777 /usr/html/cp/data/logs The 777 permission is fine, since you are most likely using nGinx. AsuraHosting customers have the "/usr/html" directory, so I'm guessing you're one of our clients. We offer free FluxCP installation, so just open a support ticket and request it.

Hi banana321, Well, the issue is that your client isn't even attempting to connect to your emulator hosted on your PC. So I'd recommend that you double-check on the clientinfo.xml to make sure it's correct and has no errors. Also that your client is properly reading from the data folder.

Hi panducakep, You need to make sure that you are using the correct version of FluxCP. You'll need the original FluxCP for eAthena, and either CalciumKid/Xantara's FluxCP for rAthena. The more obvious issue for login is to check is whether you have MD5-encrypted passwords, and if your FluxCP is using MD5 or not. Within "/config/servers.php", make sure the MD5 value reflects on whether you are using it or not for your RO account passwords.

Hi Xii, Please take a look at the .SQL files you are running. It should be clear that it is only modifying the structure or converting values of your current RO database tables. There is absolutely no indication of data modification whatsoever; and I choose to believe that the rAthena developers are smart enough to make sure that the SQL upgrades that they issue, does not ruin your data.

Hi banana321, Is your client set to read from the data folder first? If not, then it may be ignoring your clientinfo.xml and reading the one inside your custom .grf instead.

Hi Xii, Yes.

Hi Xii, The same way you imported any .SQL file to your MySQL database. Just make sure you run the upgrade .SQL files with your Ragnarok database selected.

Hi curiosity, Why not host a demo so that we can all test? If you need a VPS, feel free to let us know; we'd be more than happy to sponsor another cool project.

Hi banana321, What IP did you use in the clientinfo.xml? Also, do you have an extra clientinfo.xml in your /data folder? (This may prevent your client from connecting to the right server.)

Hi Xii, You would have to run every .sql upgrade file which is above SVN #15241, from here; http://svn.code.sf.net/p/rathena/svn/trunk/sql-files/upgrades/

Hi Xyndor, Ah alright. If you need any help with the Trial package; please let me know!

Hi Xyndor, Have you set up port forwarding for your map/char ports?

Hi Xyndor, Make sure you are using the WAN IP and not "192.168.1.226". You shouldn't be using the bind_ip, it should be commented out. //bind_ip: