Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

Starting AEM on port 6000

Avatar

Level 2

Hi,

Is there any exhaustive list of ports where AEM can be started?  I am starting aem(version 6.1 and 6.2) on port 6000 and it gives error "site cannot be reached".

Thanks 

1 Accepted Solution

Avatar

Correct answer by
Level 2

PuzanovsP wrote...

Agree with Edubey,

Tested on Mac, application registers with the Network card as it should:

192:author puzanov$ sudo lsof -i :6000 # checks port 6000
COMMAND   PID    USER   FD   TYPE             DEVICE SIZE/OFF NODE NAME
java    17925 puzanov  490u  IPv6 0x76ace7b77e8108e5      0t0  TCP *:6000 (LISTEN)

Log's also indicate no problem registering to this port.

The problem seems to be with Browsers themselves as Firefox tells us:

This address uses a network port which is normally used for purposes other than Web browsing. Firefox has canceled the request for your protection.

This stackoverflow thread covers port 6000[0][1]

http://superuser.com/questions/188058/which-ports-are-considered-unsafe-on-chrome

http://stackoverflow.com/questions/4313403/why-do-browsers-block-some-ports/22622633#22622633

Regards,

Peter

 

Seems like port 6000 is reserved for x11. Thanks Peter for the information. :)

View solution in original post

3 Replies

Avatar

Level 10

Here is snippet from docs:

The default port for AEM is 4502. If that port is not available or already in use, Quickstart automatically configures itself to use the first available port number as follows: 4502, 8080, 8081, 8082, 8083, 8084, 8085, 8888, 9362, <random>

Avatar

Community Advisor

Agree with Edubey,

Tested on Mac, application registers with the Network card as it should:

192:author puzanov$ sudo lsof -i :6000 # checks port 6000
COMMAND   PID    USER   FD   TYPE             DEVICE SIZE/OFF NODE NAME
java    17925 puzanov  490u  IPv6 0x76ace7b77e8108e5      0t0  TCP *:6000 (LISTEN)

Log's also indicate no problem registering to this port.

The problem seems to be with Browsers themselves as Firefox tells us:

This address uses a network port which is normally used for purposes other than Web browsing. Firefox has canceled the request for your protection.

This stackoverflow thread covers port 6000[0][1]

http://superuser.com/questions/188058/which-ports-are-considered-unsafe-on-chrome

http://stackoverflow.com/questions/4313403/why-do-browsers-block-some-ports/22622633#22622633

Regards,

Peter

Avatar

Correct answer by
Level 2

PuzanovsP wrote...

Agree with Edubey,

Tested on Mac, application registers with the Network card as it should:

192:author puzanov$ sudo lsof -i :6000 # checks port 6000
COMMAND   PID    USER   FD   TYPE             DEVICE SIZE/OFF NODE NAME
java    17925 puzanov  490u  IPv6 0x76ace7b77e8108e5      0t0  TCP *:6000 (LISTEN)

Log's also indicate no problem registering to this port.

The problem seems to be with Browsers themselves as Firefox tells us:

This address uses a network port which is normally used for purposes other than Web browsing. Firefox has canceled the request for your protection.

This stackoverflow thread covers port 6000[0][1]

http://superuser.com/questions/188058/which-ports-are-considered-unsafe-on-chrome

http://stackoverflow.com/questions/4313403/why-do-browsers-block-some-ports/22622633#22622633

Regards,

Peter

 

Seems like port 6000 is reserved for x11. Thanks Peter for the information. :)