You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by "William Greene (JIRA)" <ji...@apache.org> on 2015/05/04 04:31:05 UTC

[jira] [Commented] (APLO-378) unable to access web interface, new install

    [ https://issues.apache.org/jira/browse/APLO-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14526182#comment-14526182 ] 

William Greene commented on APLO-378:
-------------------------------------

FYI:  when accessing
INFO  | Administration interface available at: https://127.0.0.1:61681/
INFO  | Administration interface available at: http://127.0.0.1:61680/

(switching 127.0.0.1 for the machines ip address,    i just receive no response from server message.

older version of activemq  (5?)   worked fine right out of the box on this same machine.... NO funny work with iptables/etc.... it just worked.


After having my failures, i even tried opening firewall rules for the two ports and still did not work...  (again, i did not have to do this before with older versions before fork to apollo

root@debian:/home/william/mq# iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere             state RELATED,ESTABLISHED
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:http
ACCEPT     tcp  --  anywhere             anywhere             state NEW tcp dpt:ssh
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:61681
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:61680

> unable to access web interface, new install
> -------------------------------------------
>
>                 Key: APLO-378
>                 URL: https://issues.apache.org/jira/browse/APLO-378
>             Project: ActiveMQ Apollo
>          Issue Type: Bug
>          Components: apollo-web
>    Affects Versions: 1.7.1
>         Environment: INFO  | OS     : Linux 3.16.0-4-amd64 (Debian GNU/Linux 8.0 (jessie))
> INFO  | JVM    : OpenJDK 64-Bit Server VM 1.7.0_79 (Oracle Corporation)
> INFO  | Apollo : 1.7.1 (at: /home/william/mq/apache-apollo-1.7.1)
>            Reporter: William Greene
>
> I cant access the web interface from outside machine on LOCAL network.
> Followed instructions on:
> http://activemq.apache.org/apollo/documentation/getting-started.html
> Fresh machine:  able to access apache webserver via machien IP address port 80, unable to access apollo.
> Following works LOCALLY from machine.  NOT externally (when switching localhost for ip of machine)
> root@debian:/var/lib/mybroker/log# curl -u "admin:password" \
> > 'http://localhost:61680/broker/connections.json?f=id&f=read_counter'
> {"page":0,"page_size":100,"total_pages":1,"total_rows":0,"headers":["id","read_counter"],"rows":[]}
> STARTUP of apollo message:
> ###############################
> Loading configuration file '/home/william/mq/test/mybroker/etc/apollo.xml'.
> INFO  | OS     : Linux 3.16.0-4-amd64 (Debian GNU/Linux 8.0 (jessie))
> INFO  | JVM    : OpenJDK 64-Bit Server VM 1.7.0_79 (Oracle Corporation)
> INFO  | Apollo : 1.7.1 (at: /home/william/mq/apache-apollo-1.7.1)
> INFO  | OS is restricting the open file limit to: 50000
> INFO  | Starting store: leveldb store at /home/william/mq/test/mybroker/data
> INFO  | Accepting connections at: tcp://0.0.0.0:61613
> INFO  | Accepting connections at: tls://0.0.0.0:61614
> INFO  | Accepting connections at: ws://0.0.0.0:61623/
> INFO  | Accepting connections at: wss://0.0.0.0:61624/
> INFO  | Administration interface available at: https://127.0.0.1:61681/
> INFO  | Administration interface available at: http://127.0.0.1:61680/
> ####################
> root@debian:/home/william/mq# ifconfig
> eth0      Link encap:Ethernet  HWaddr ########
>           inet addr:10.0.0.2  Bcast:10.0.0.255  Mask:255.255.255.0
> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
> may not be a bug, but suggestions on how to overcome this, would be beneficial on the how to guide...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)