PDA

View Full Version : Connecting to EoC2


Excuses
08-07-2016, 11:13 PM
Hey,


I have followed all directions to connect to EoC2, first time i try is gives me an error that cannot connect, the 2nd attempt returns green and says connected with etc.etc.etc info.

The login button however, doesn't do anything. Am i connecting properly?

Does it have to be eoc_database_user info?

Excuses
08-08-2016, 12:53 AM
Nevermind, i have fixed it=)

allahn
04-22-2017, 09:06 PM
I cannot for the life of my figure out how to login to that thing. Any help? All of the fields are correct, ports are fine, etc. regardless, I get the dreaded:

Cannot connect to server!
Cannot connect to database peq

Any ideas?

DominionZ
05-04-2017, 01:52 PM
Having the same problem here. Followed the guide and set everything up but no dice.
Cannot connect to server
Cannot connect to database peq

Any help is appreciated

Raghnar
11-08-2017, 04:36 PM
This has happened to me a few times. I always forget what I did to fix it. It just happened today so after I unplugged my head from my butt and remembered I decided I would post it to see if it might help you.

When you set up your port forwarding, were you certain that the port you opened was for the box you were hosting the database on? It isn't always xxx.xxx.1.1.

Also after a less than graceful shutdown and disordered restart your router might end up assigning a different internal IP to your host machine, and EOC will be trying to connect to your db but being directed to your cellphone, laptop, or in my case to my solar inverter's monitor.

Lane
12-29-2017, 03:18 PM
Bump. Please help

I've followed the instructions, see my user info in the user table of SQL but can't connect. :(

dominionofsouls
08-17-2018, 03:06 PM
Same issue here. I'm sure the solution is simple but it has stumped me.

Edit. Figured it out. I initially jacked up my port forwarding rules (UDP vice TCP). I also had two firewalls to edit; the firewall in my computer's anti-virus software and the firewall in my router.

Rikon
05-13-2020, 12:52 PM
How are folks setting up iptables to get this to work. I don't want 3306 open to the world and limit it to my server and EOC.

-A INPUT -s 172.20.0.12/32 -p udp -m udp --dport 3306 -j ACCEPT
-A INPUT -s 172.20.0.12/32 -p tcp -m tcp --dport 3306 -j ACCEPT
-A OUTPUT -s 172.20.0.12/32 -p udp -m udp --dport 3306 -j ACCEPT
-A OUTPUT -s 172.20.0.12/32 -p tcp -m tcp --dport 3306 -j ACCEPT