Ubiquity Unify Windows controller - service not starting

[iSteve]

Hi all,

 

I have inherited a Unify controller which is running on a Windows PC, servicing 15 AC-PRO access points. Today I wanted to sign in to the controller's web page but it was not accessible (signing in at localhost, RDP-ing on to the box).

The UbiquityUnify2 and Unifi Controller services are stopped and do not restart. Rebooting has no effect -services still don't start

 

There is a 'start ubiquity' batch file. If you run this as administrator, it takes ages to do anything, then returns "Port 8080 is not available". Services don't start. Sign in page still not available.

The localhost controller webpage says connection refused.

 

Being new to Ubiquity:

1) Should the services start on their own? They're set to Automatic in services.msc

2) Do I have to run the 'start ubiquity' batch file, or should it be the services running the show?

3) Why does this seem to have spontaneously died?

 

Any advice welcome

[ZeroHour]

Possibly an old version of Java?

If I recall Java had expiry dates in the old days to try and force people to upgrade because of all the holes.

[Michael]

Agreed - make sure you install a 64Bit version of Java as a starting point.

 

If that still fails, apply an upgrade over the existing install.

[DGardiner]

Hi all,

 

I have inherited a Unify controller which is running on a Windows PC, servicing 15 AC-PRO access points. Today I wanted to sign in to the controller's web page but it was not accessible (signing in at localhost, RDP-ing on to the box).

The UbiquityUnify2 and Unifi Controller services are stopped and do not restart. Rebooting has no effect -services still don't start

 

There is a 'start ubiquity' batch file. If you run this as administrator, it takes ages to do anything, then returns "Port 8080 is not available". Services don't start. Sign in page still not available.

The localhost controller webpage says connection refused.

 

Being new to Ubiquity:

1) Should the services start on their own? They're set to Automatic in services.msc

2) Do I have to run the 'start ubiquity' batch file, or should it be the services running the show?

3) Why does this seem to have spontaneously died?

 

Any advice welcome

something is already bound to port 8080 so its not starting, you need to find and reconfigure whatever it is

[howartp]

If you have services with those names, you're seemingly on a newer version than I am as there's no "Unifi" services on any windows controller i've seen.

 

Therefore what I say may be out of date, but...

 

Unifi controller is hardcoded to need Java 8; you can't upgrade to 9/10/11.

 

If Windows/Java has updated java then you'll need to roll it back.

 

As I say, things may have moved on if you're on controller v7.

[Foresthippy]

If you have services with those names, you're seemingly on a newer version than I am as there's no "Unifi" services on any windows controller i've seen.

 

I think the controller is just a java app out of the box, but there are destructions online on how to convert it to a service.

[jonnykewell1]

I've also found killing all java instances and then starting the controller again sometimes kicks it back into life but as above, get it converted into a service.