Jump to content

Server dont work


TARDIS_official
  • Version: Beta 4 Closed Suggestion

I changed the IP in the client folder to my ip, the port put it into my router (5400). If I start the server, I write that UPnP has been successfully activated, and I really can not see these ports in UPnP, because I write the server is not available. The firewall is disabled, please help!

///////////////////////////////////////////////////
Console:
Copyright (C) 2017  Ascension Game Dev
Version 0.4.7.0
For help, support, and updates visit: http://ascensiongamedev.com
Loading, please wait.
Formulas.xml missing. Generated default formulas file.
No classes found! - Creating a default class!
No maps found! - Creating an empty map!
Server has 0 registered players.
Game time is now: Wednesday, December 27, 2017 9:33:30 PM
Websocket listener started for Unity WebGL Clients using Port #5400

UPnP Service Initialization Succeeded
Successfully auto port forwarded tcp port 5400 using UPnP.
Successfully auto port forwarded udp port 5400 using UPnP.

Connection Information:
   Public IP: 193.42.156.10
   Public Port: 5400

It does not appear that your game is accessible to the outside world.
Debugging Steps (To allow public access):
   1. Firewalls might be blocking connections to your server. Check firewalls on your system. (i.e. iptables, FirewallD, Windows Firewall)
   2. Antivirus programs might also be blocking connections and you may need to add Intersect Server.exe to your antivirus exclusions.
   3. If on a college campus, or within a business network you likely do not have permission to open ports or host games in which case you are screwed!


Server Started. Using Port #5400
Type exit to shutdown the server, or help for a list of commands.
>


////////////////////////////////////////////////////

Intersect Client-2017_12_27-21_33_48_922.log

Intersect Server-2017_12_27-21_33_31_021.log

Edited by TARDIS_official
Errors



User Feedback

Recommended Comments

You seem to be launching Intersect for the first time (If you aren't I apologize, but for simplicity's sake, let's suppose you are) Several things can keep the server from working if you're not hooking up to 'localhost':

  1. The first, you already mentioned - the firewall. Check that it isn't the problem by completely disabling it (it looks like you have)
  2. The second is through your antivirus software. You can add the Server.exe to the exceptions on your antivirus software as suggested, or completely disable it to test.
  3. As it says in the display text, you might also be at the mercy of some other institution's firewalls or exceptions, in which case, you very likely won't be able to change any of the outcomes here, anyway (most common on college campuses or at a place of business/public WiFi, etc)...
  4. The final problem might be found in your router, itself. Lots of commercial routers doled out by internet providers put their own junk in their hardware which gets in the way of would-be game hosts. Comcast, for example. The workaround for this is typically to buy your own router/modem or set your router to 'bridge mode' in its console, which uses the modem-only.

It is recommended you only do the first two steps temporarily, to see if you can locate the issue, and drill-down from there if turning one or the other off completely solves the problem.

 

The third and fourth options are fairly common as well, but might mean you're out of luck or at least stuck with spending some extra dough to get your server running. Note that JC and the team now host servers at very reasonable prices, when you're ready to launch your game. Until then, you really should be building/testing locally, anyway. :)

Hope this helps!

Share this comment


Link to comment
Share on other sites
On 31.12.2017 at 7:55 PM, EVOLV said:

You seem to be launching Intersect for the first time (If you aren't I apologize, but for simplicity's sake, let's suppose you are) Several things can keep the server from working if you're not hooking up to 'localhost':

  1. The first, you already mentioned - the firewall. Check that it isn't the problem by completely disabling it (it looks like you have)
  2. The second is through your antivirus software. You can add the Server.exe to the exceptions on your antivirus software as suggested, or completely disable it to test.
  3. As it says in the display text, you might also be at the mercy of some other institution's firewalls or exceptions, in which case, you very likely won't be able to change any of the outcomes here, anyway (most common on college campuses or at a place of business/public WiFi, etc)...
  4. The final problem might be found in your router, itself. Lots of commercial routers doled out by internet providers put their own junk in their hardware which gets in the way of would-be game hosts. Comcast, for example. The workaround for this is typically to buy your own router/modem or set your router to 'bridge mode' in its console, which uses the modem-only.

It is recommended you only do the first two steps temporarily, to see if you can locate the issue, and drill-down from there if turning one or the other off completely solves the problem.

 

The third and fourth options are fairly common as well, but might mean you're out of luck or at least stuck with spending some extra dough to get your server running. Note that JC and the team now host servers at very reasonable prices, when you're ready to launch your game. Until then, you really should be building/testing locally, anyway. :)

Hope this helps!

it's don't help :c but UPnP enabled 

Share this comment


Link to comment
Share on other sites


Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×