can't start server properly after install on Vista

[stevem]

I am brand new to ElectroServer - installing to get to grips with it ready for a new job. I've installed on Vista, but when I start the server, I get the following error:

20:17:54,063 [pool-1-thread-2] ERROR com.electrotank.electroserver4.servers.gateway.Gat ewayServer - Failed opening a listener on /127.0.0.1:1935

I've tried all the usual Vista security things but no luck. Tried running the server as administrator with no success. If I try to open the Web Administrator, I get as far as the invalid certificate, but after that it's an empty page, or rather empty html - I get the base tags only:
[b]</body>

I'm sure it's something simple - but I can't find any other posts in this forum with the same problem

[MikeParks]

When you open the web admin, are you sure that you're using the connection type specified in ES4Configuration.xml? If SSL is true, use https://localhost:8080/ otherwise use http://localhost:8080/.

[stevem]

Thanks for the quick response Mike.

I've just checked the configuration file and it is definitely port 8080 and SSL enabled true. When I try https://localhost:8080/ I get Page Load Error Connection Refused. I don't think the server is even running as the command window doesn't display any message to that effect. This is the entire display after a startup attempt:

20:44:35,204 [main] INFO DisplayLogger -
-=-=-=-=-=-=-=-
Starting ElectroServer 4.0.6
Go to http://www.electro-server.com/ for the newest version.
-=-=-=-=-=-=-=-
Computer Information
Operating System: Windows Vista
Operating System Architecture: x86
Processors Available: 2
Memory Available: 63Mb
-=-=-=-=-=-=-=-
Virtual Machine Information
Virtual Machine Vendor: Sun Microsystems Inc.
Virtual Machine Version: 1.6.0_03


20:44:39,713 [pool-1-thread-1] ERROR com.electrotank.electroserver4.servers.gate
way.GatewayServer - Failed opening a listener on /127.0.0.1:1935

[MikeParks]

When installing, did you install as Professional or Enterprise? Just trying to verify the install steps while I test on my Vista machine.

[stevem]

Professional - and all defaults apart from web admin login details and installing the standalone (which is now set to start manually on startup). The first time I installed the server, I didn't install the standalone and had an identical problem.

[MikeParks]

Are you currently running any other services, such as Adobe's Flash Media Server? If so, this could already be using 1935. You may want to try disabling it or removing the 1935 listener from ElectroServer.

[stevem]

Yup, FMS was running as a service - I stopped it and ElectroServer is now starting successfully. But I still can't get web administrator to open. I get the invalid certificate ok, but then I just get the empty html tags.

[MikeParks]

Could you try turning SSL to false in the configuration to see if it makes a difference?

[stevem]

Yes it does make a difference but still not behaving as expected. IE7 just displays some weird characters, and FF informs me that I have chosen to open admin which is a: application/octet-stream and asks if I want to save the file or browse for an app to open it.

Thanks for your time with this Mike.

[MikeParks]

If you've set to SSL as true in ES4Configuration.xml, accessing ElectroServer via http rather than https will start feeding the SSL data to your client. Be sure that you access it as
https://localhost:port/admin/ depending on the host/port settings in said XML file.

[stevem]

This is very strange - I assume this problem is unusual. So, I have tried different combinations in the configuration file, I have tried setting the Ssl enabled attribute to both true and false, using the corresponding https and http protocols with each - and making sure I restart the server after each change. Still nothing.

Then I tried an SSL connection using a different port (1234) changing the url to https://localhost:1234/admin/ (after restarting the server) - Firefox gives me the 'Failed to connect' error, followed by 'The connection was refused when attempting to connect to localhost:1234'.

I am not using a firewall on my local machine (only the one on the router) so it can't be a firewall issue. I have given all possible users full control in the Vista security settings for the entire ElectroServer_4_0_6 directory, subfolders and files, and tried running the server as administrator. All to no avail!

[MikeParks]

Could I get you to do a fresh install of ElectroServer? I just ran another one on my Vista machine and I'm still able to manage things normally. Don't make any modifications to the ES4Configuration.xml. Just give the server a run and head in via https://localhost:8080/admin/ as soon as the console says it's started.

[stevem]

Did the trick Mike, thanks a lot. I decided to uninstall, download a fresh exe, and then re-install, and made sure the FMS service was stopped, and it all came good. I've no idea what the problem was, but all's working now, so I look forward to trying it out.

Thanks again for your time and patience!

[MikeParks]

Not a problem. That's why I'm here. Have fun with ElectroServer.

[mavor]

I am also running into this problem. Fresh install, straight to the link that you provided but firefox and IE give me the exact same problems that the above poster has faced. I didn't change anything in the config file at all.

It's very strange, because the server reports starting perfectly fine... :(

[mavor]

Er just one quick addition... If I start my computer with the ES 4.0.6 standalone service running in the background, i can't start the server. I have to stop the standalone service process in order to start the server.


**Edit: Ok i fixed it by replacing "localhost" with "127.0.0.1" in the browser address bar. Firefox came up with a bogus certificate error but i was able to add my localhost to the exception list (lol) and now i am able to connect fine.

However i still cannot connect by using "localhost" instead of "127.0.0.1" ... what gives?: )

[MikeParks]

You won't be able to run 2 instance of the same server install as they're using the same settings. I'd only use the background service mode if you're on a final deployment of your app and have no need to see the console while it's running. During development of your app, however, it's suggested to run it standalone rather than as a service in the event you have an error message or the like noted in your console.

As for the localhost vs 127.0.0.1 thing, it shouldn't make a difference since they both mean the same thing. Just continue using 127.0.0.1. My advice would be to make a bookmark to the web admin so you don't have to type it all the time.