You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Christopher Pisz <ch...@gmail.com> on 2020/08/21 13:54:33 UTC
remotely access web console
I really want to be able to access the web console remotely for my
development testing.
I read this:
https://activemq.apache.org/components/artemis/documentation/latest/management-console.html
and it took me to this:
https://jolokia.org/reference/html/security.html
I created a file called etc/jolokia-access.xml and I put:
<remote>
<host>localhost</host>
<host>ip that showed in ifconfig under ppp0</host>
</remote>
I also opened port 8161 in the firewall.
However, when I open a browser and put in http://machine.domain.com:8161 I
got connection refused.
I can bring up the console locally if someone goes to the machine.
People onsite can ssh -X and get firefox working and then bring it up
locally. I cannot SSH -X firefox for whatever reason, it is completely
unresponsive, which is why I wanted to configure it somehow to just let me
use my own browser and access the page.
Any suggestions?
Re: remotely access web console
Posted by Christopher Pisz <ch...@gmail.com>.
Ah, I got it.
Had to dump the browser cache and restart artemis. All set. Thanks!
On Fri, Aug 21, 2020 at 12:27 PM Christopher Pisz <ch...@gmail.com>
wrote:
> I edited <broker directory>/etc/jolokia-access.xml
>
> <!-- This policy file controls the Jolokia JMX-HTTP bridge security
> options for the web console.
> see: https://jolokia.org/reference/html/security.html -->
> <restrict>
>
> <cors>
> <!-- Allow cross origin access from localhost ... -->
> <allow-origin>*://*</allow-origin>
>
>
> <!-- Options from this point on are auto-generated by Create.java
> from the Artemis CLI -->
> <!-- Check for the proper origin on the server side, too -->
> <strict-checking/>
> </cors>
>
> But it didn't change the end result :/
>
>
> On Fri, Aug 21, 2020 at 12:12 PM Christopher Pisz <
> christopherpisz@gmail.com> wrote:
>
>> Awe. I celebrated too soon. Once I logged in and went to Management
>> Console, it told me:
>>
>> "This page allows you to connect to remote processes which *already have
>> a jolokia agent <http://jolokia.org/> running inside them*. You will
>> need to know the host name, port and path of the jolokia agent to be able
>> to connect.
>>
>> If the process you wish to connect to does not have a jolokia agent
>> inside, please refer to the jolokia documentation
>> <http://jolokia.org/agent.html> for how to add a JVM, servlet or OSGi
>> based agent inside it.
>>
>> The *Local Tab* is not currently enabled because either the server side *hawtio-local-jvm-mbean
>> plugin* is not installed or this JVM cannot find the
>> *com.sun.tools.attach.VirtualMachine* API usually found in the *tool.jar*.
>> Please see the FAQ entry <http://hawt.io/faq/index.html> for more
>> details."
>>
>> It then gave me a bunch of errors about "Cannot get property"
>>
>> On Fri, Aug 21, 2020 at 11:53 AM Christopher Pisz <
>> christopherpisz@gmail.com> wrote:
>>
>>> Hell yes! Thank you so much.
>>>
>>> On Fri, Aug 21, 2020 at 11:49 AM Jean-Baptiste Onofre <jb...@nanthrax.net>
>>> wrote:
>>>
>>>> Oh sorry, I thought you used ActiveMQ "classic", not Artemis.
>>>>
>>>> About Artemis, you have to use 0.0.0.0 instead of localhost to bind on
>>>> any interface.
>>>>
>>>> Regards
>>>> JB
>>>>
>>>> > Le 21 août 2020 à 16:33, Christopher Pisz <ch...@gmail.com>
>>>> a écrit :
>>>> >
>>>> > <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
>>>> > <!--
>>>> > ~ Licensed to the Apache Software Foundation (ASF) under one or more
>>>> > ~ contributor license agreements. See the NOTICE file distributed
>>>> with
>>>> > ~ this work for additional information regarding copyright ownership.
>>>> > ~ The ASF licenses this file to You under the Apache License,
>>>> Version 2.0
>>>> > ~ (the "License"); you may not use this file except in compliance
>>>> with
>>>> > ~ the License. You may obtain a copy of the License at
>>>> > ~
>>>> > ~ http://www.apache.org/licenses/LICENSE-2.0
>>>> > ~
>>>> > ~ Unless required by applicable law or agreed to in writing, software
>>>> > ~ distributed under the License is distributed on an "AS IS" BASIS,
>>>> > ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
>>>> implied.
>>>> > ~ See the License for the specific language governing permissions and
>>>> > ~ limitations under the License.
>>>> > -->
>>>> >
>>>> > <broker xmlns="http://activemq.org/schema">
>>>> >
>>>> > <jaas-security domain="activemq"/>
>>>> >
>>>> > <!-- artemis.URI.instance is parsed from artemis.instance by the CLI
>>>> > startup.
>>>> > This is to avoid situations where you could have spaces or
>>>> special
>>>> > characters on this URI -->
>>>> > <server configuration="file:/var/lib/testbroker/etc//broker.xml"/>
>>>> >
>>>> > <!-- The web server is only bound to localhost by default -->
>>>> > <web bind="http://localhost:8161" path="web">
>>>> > <app url="activemq-branding" war="activemq-branding.war"/>
>>>> > <app url="artemis-plugin" war="artemis-plugin.war"/>
>>>> > <app url="console" war="console.war"/>
>>>> > </web>
>>>> >
>>>> >
>>>> > </broker>
>>>> >
>>>> > I imagine I need to put something in the <web> section to bind. Not
>>>> sure
>>>> > what to put.
>>>> >
>>>> >
>>>> > On Fri, Aug 21, 2020 at 10:23 AM Justin Bertram <jb...@apache.org>
>>>> wrote:
>>>> >
>>>> >> You're using Artemis right? Artemis doesn't have that config file.
>>>> The
>>>> >> embedded web server is configured in bootstrap.xml. Can you paste
>>>> your
>>>> >> bootstrap.xml?
>>>> >>
>>>> >>
>>>> >> Justin
>>>> >>
>>>> >> On Fri, Aug 21, 2020 at 9:12 AM Christopher Pisz <
>>>> >> christopherpisz@gmail.com>
>>>> >> wrote:
>>>> >>
>>>> >>> Either I don't have Jetty installed or I don't know where to find
>>>> the
>>>> >>> config file you refer to.
>>>> >>> Yes I can curl http://localhost:8161
>>>> >>>
>>>> >>>
>>>> >>> On Fri, Aug 21, 2020 at 10:01 AM Jean-Baptiste Onofre <
>>>> jb@nanthrax.net>
>>>> >>> wrote:
>>>> >>>
>>>> >>>> Hi,
>>>> >>>>
>>>> >>>> Can you check that you have 0.0.0.0 for jettyPort/host in
>>>> >> conf/jetty.xml
>>>> >>> ?
>>>> >>>>
>>>> >>>> Are you able to access the port locally using curl
>>>> >>>> http://localhost:8161/admin <http://localhost:8161/admin> for
>>>> >> instance ?
>>>> >>>>
>>>> >>>> Regards
>>>> >>>> JB
>>>> >>>>
>>>> >>>>> Le 21 août 2020 à 15:54, Christopher Pisz <
>>>> christopherpisz@gmail.com
>>>> >>>
>>>> >>> a
>>>> >>>> écrit :
>>>> >>>>>
>>>> >>>>> I really want to be able to access the web console remotely for my
>>>> >>>>> development testing.
>>>> >>>>>
>>>> >>>>> I read this:
>>>> >>>>>
>>>> >>>>
>>>> >>>
>>>> >>
>>>> https://activemq.apache.org/components/artemis/documentation/latest/management-console.html
>>>> >>>>>
>>>> >>>>> and it took me to this:
>>>> >>>>> https://jolokia.org/reference/html/security.html
>>>> >>>>>
>>>> >>>>> I created a file called etc/jolokia-access.xml and I put:
>>>> >>>>>
>>>> >>>>> <remote>
>>>> >>>>> <host>localhost</host>
>>>> >>>>> <host>ip that showed in ifconfig under ppp0</host>
>>>> >>>>> </remote>
>>>> >>>>>
>>>> >>>>>
>>>> >>>>> I also opened port 8161 in the firewall.
>>>> >>>>>
>>>> >>>>> However, when I open a browser and put in
>>>> >>> http://machine.domain.com:8161
>>>> >>>> I
>>>> >>>>> got connection refused.
>>>> >>>>>
>>>> >>>>> I can bring up the console locally if someone goes to the machine.
>>>> >>>>> People onsite can ssh -X and get firefox working and then bring
>>>> it up
>>>> >>>>> locally. I cannot SSH -X firefox for whatever reason, it is
>>>> >> completely
>>>> >>>>> unresponsive, which is why I wanted to configure it somehow to
>>>> just
>>>> >> let
>>>> >>>> me
>>>> >>>>> use my own browser and access the page.
>>>> >>>>>
>>>> >>>>> Any suggestions?
>>>> >>>>
>>>> >>>>
>>>> >>>
>>>> >>
>>>>
>>>>
Re: remotely access web console
Posted by Christopher Pisz <ch...@gmail.com>.
I edited <broker directory>/etc/jolokia-access.xml
<!-- This policy file controls the Jolokia JMX-HTTP bridge security options
for the web console.
see: https://jolokia.org/reference/html/security.html -->
<restrict>
<cors>
<!-- Allow cross origin access from localhost ... -->
<allow-origin>*://*</allow-origin>
<!-- Options from this point on are auto-generated by Create.java
from the Artemis CLI -->
<!-- Check for the proper origin on the server side, too -->
<strict-checking/>
</cors>
But it didn't change the end result :/
On Fri, Aug 21, 2020 at 12:12 PM Christopher Pisz <ch...@gmail.com>
wrote:
> Awe. I celebrated too soon. Once I logged in and went to Management
> Console, it told me:
>
> "This page allows you to connect to remote processes which *already have
> a jolokia agent <http://jolokia.org/> running inside them*. You will need
> to know the host name, port and path of the jolokia agent to be able to
> connect.
>
> If the process you wish to connect to does not have a jolokia agent
> inside, please refer to the jolokia documentation
> <http://jolokia.org/agent.html> for how to add a JVM, servlet or OSGi
> based agent inside it.
>
> The *Local Tab* is not currently enabled because either the server side *hawtio-local-jvm-mbean
> plugin* is not installed or this JVM cannot find the
> *com.sun.tools.attach.VirtualMachine* API usually found in the *tool.jar*.
> Please see the FAQ entry <http://hawt.io/faq/index.html> for more
> details."
>
> It then gave me a bunch of errors about "Cannot get property"
>
> On Fri, Aug 21, 2020 at 11:53 AM Christopher Pisz <
> christopherpisz@gmail.com> wrote:
>
>> Hell yes! Thank you so much.
>>
>> On Fri, Aug 21, 2020 at 11:49 AM Jean-Baptiste Onofre <jb...@nanthrax.net>
>> wrote:
>>
>>> Oh sorry, I thought you used ActiveMQ "classic", not Artemis.
>>>
>>> About Artemis, you have to use 0.0.0.0 instead of localhost to bind on
>>> any interface.
>>>
>>> Regards
>>> JB
>>>
>>> > Le 21 août 2020 à 16:33, Christopher Pisz <ch...@gmail.com>
>>> a écrit :
>>> >
>>> > <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
>>> > <!--
>>> > ~ Licensed to the Apache Software Foundation (ASF) under one or more
>>> > ~ contributor license agreements. See the NOTICE file distributed with
>>> > ~ this work for additional information regarding copyright ownership.
>>> > ~ The ASF licenses this file to You under the Apache License, Version
>>> 2.0
>>> > ~ (the "License"); you may not use this file except in compliance with
>>> > ~ the License. You may obtain a copy of the License at
>>> > ~
>>> > ~ http://www.apache.org/licenses/LICENSE-2.0
>>> > ~
>>> > ~ Unless required by applicable law or agreed to in writing, software
>>> > ~ distributed under the License is distributed on an "AS IS" BASIS,
>>> > ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
>>> implied.
>>> > ~ See the License for the specific language governing permissions and
>>> > ~ limitations under the License.
>>> > -->
>>> >
>>> > <broker xmlns="http://activemq.org/schema">
>>> >
>>> > <jaas-security domain="activemq"/>
>>> >
>>> > <!-- artemis.URI.instance is parsed from artemis.instance by the CLI
>>> > startup.
>>> > This is to avoid situations where you could have spaces or
>>> special
>>> > characters on this URI -->
>>> > <server configuration="file:/var/lib/testbroker/etc//broker.xml"/>
>>> >
>>> > <!-- The web server is only bound to localhost by default -->
>>> > <web bind="http://localhost:8161" path="web">
>>> > <app url="activemq-branding" war="activemq-branding.war"/>
>>> > <app url="artemis-plugin" war="artemis-plugin.war"/>
>>> > <app url="console" war="console.war"/>
>>> > </web>
>>> >
>>> >
>>> > </broker>
>>> >
>>> > I imagine I need to put something in the <web> section to bind. Not
>>> sure
>>> > what to put.
>>> >
>>> >
>>> > On Fri, Aug 21, 2020 at 10:23 AM Justin Bertram <jb...@apache.org>
>>> wrote:
>>> >
>>> >> You're using Artemis right? Artemis doesn't have that config file. The
>>> >> embedded web server is configured in bootstrap.xml. Can you paste your
>>> >> bootstrap.xml?
>>> >>
>>> >>
>>> >> Justin
>>> >>
>>> >> On Fri, Aug 21, 2020 at 9:12 AM Christopher Pisz <
>>> >> christopherpisz@gmail.com>
>>> >> wrote:
>>> >>
>>> >>> Either I don't have Jetty installed or I don't know where to find the
>>> >>> config file you refer to.
>>> >>> Yes I can curl http://localhost:8161
>>> >>>
>>> >>>
>>> >>> On Fri, Aug 21, 2020 at 10:01 AM Jean-Baptiste Onofre <
>>> jb@nanthrax.net>
>>> >>> wrote:
>>> >>>
>>> >>>> Hi,
>>> >>>>
>>> >>>> Can you check that you have 0.0.0.0 for jettyPort/host in
>>> >> conf/jetty.xml
>>> >>> ?
>>> >>>>
>>> >>>> Are you able to access the port locally using curl
>>> >>>> http://localhost:8161/admin <http://localhost:8161/admin> for
>>> >> instance ?
>>> >>>>
>>> >>>> Regards
>>> >>>> JB
>>> >>>>
>>> >>>>> Le 21 août 2020 à 15:54, Christopher Pisz <
>>> christopherpisz@gmail.com
>>> >>>
>>> >>> a
>>> >>>> écrit :
>>> >>>>>
>>> >>>>> I really want to be able to access the web console remotely for my
>>> >>>>> development testing.
>>> >>>>>
>>> >>>>> I read this:
>>> >>>>>
>>> >>>>
>>> >>>
>>> >>
>>> https://activemq.apache.org/components/artemis/documentation/latest/management-console.html
>>> >>>>>
>>> >>>>> and it took me to this:
>>> >>>>> https://jolokia.org/reference/html/security.html
>>> >>>>>
>>> >>>>> I created a file called etc/jolokia-access.xml and I put:
>>> >>>>>
>>> >>>>> <remote>
>>> >>>>> <host>localhost</host>
>>> >>>>> <host>ip that showed in ifconfig under ppp0</host>
>>> >>>>> </remote>
>>> >>>>>
>>> >>>>>
>>> >>>>> I also opened port 8161 in the firewall.
>>> >>>>>
>>> >>>>> However, when I open a browser and put in
>>> >>> http://machine.domain.com:8161
>>> >>>> I
>>> >>>>> got connection refused.
>>> >>>>>
>>> >>>>> I can bring up the console locally if someone goes to the machine.
>>> >>>>> People onsite can ssh -X and get firefox working and then bring it
>>> up
>>> >>>>> locally. I cannot SSH -X firefox for whatever reason, it is
>>> >> completely
>>> >>>>> unresponsive, which is why I wanted to configure it somehow to just
>>> >> let
>>> >>>> me
>>> >>>>> use my own browser and access the page.
>>> >>>>>
>>> >>>>> Any suggestions?
>>> >>>>
>>> >>>>
>>> >>>
>>> >>
>>>
>>>
Re: remotely access web console
Posted by Christopher Pisz <ch...@gmail.com>.
Awe. I celebrated too soon. Once I logged in and went to Management
Console, it told me:
"This page allows you to connect to remote processes which *already have
a jolokia agent <http://jolokia.org/> running inside them*. You will need
to know the host name, port and path of the jolokia agent to be able to
connect.
If the process you wish to connect to does not have a jolokia agent inside,
please refer to the jolokia documentation <http://jolokia.org/agent.html> for
how to add a JVM, servlet or OSGi based agent inside it.
The *Local Tab* is not currently enabled because either the server
side *hawtio-local-jvm-mbean
plugin* is not installed or this JVM cannot find the
*com.sun.tools.attach.VirtualMachine* API usually found in the *tool.jar*.
Please see the FAQ entry <http://hawt.io/faq/index.html> for more details."
It then gave me a bunch of errors about "Cannot get property"
On Fri, Aug 21, 2020 at 11:53 AM Christopher Pisz <ch...@gmail.com>
wrote:
> Hell yes! Thank you so much.
>
> On Fri, Aug 21, 2020 at 11:49 AM Jean-Baptiste Onofre <jb...@nanthrax.net>
> wrote:
>
>> Oh sorry, I thought you used ActiveMQ "classic", not Artemis.
>>
>> About Artemis, you have to use 0.0.0.0 instead of localhost to bind on
>> any interface.
>>
>> Regards
>> JB
>>
>> > Le 21 août 2020 à 16:33, Christopher Pisz <ch...@gmail.com>
>> a écrit :
>> >
>> > <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
>> > <!--
>> > ~ Licensed to the Apache Software Foundation (ASF) under one or more
>> > ~ contributor license agreements. See the NOTICE file distributed with
>> > ~ this work for additional information regarding copyright ownership.
>> > ~ The ASF licenses this file to You under the Apache License, Version
>> 2.0
>> > ~ (the "License"); you may not use this file except in compliance with
>> > ~ the License. You may obtain a copy of the License at
>> > ~
>> > ~ http://www.apache.org/licenses/LICENSE-2.0
>> > ~
>> > ~ Unless required by applicable law or agreed to in writing, software
>> > ~ distributed under the License is distributed on an "AS IS" BASIS,
>> > ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
>> implied.
>> > ~ See the License for the specific language governing permissions and
>> > ~ limitations under the License.
>> > -->
>> >
>> > <broker xmlns="http://activemq.org/schema">
>> >
>> > <jaas-security domain="activemq"/>
>> >
>> > <!-- artemis.URI.instance is parsed from artemis.instance by the CLI
>> > startup.
>> > This is to avoid situations where you could have spaces or
>> special
>> > characters on this URI -->
>> > <server configuration="file:/var/lib/testbroker/etc//broker.xml"/>
>> >
>> > <!-- The web server is only bound to localhost by default -->
>> > <web bind="http://localhost:8161" path="web">
>> > <app url="activemq-branding" war="activemq-branding.war"/>
>> > <app url="artemis-plugin" war="artemis-plugin.war"/>
>> > <app url="console" war="console.war"/>
>> > </web>
>> >
>> >
>> > </broker>
>> >
>> > I imagine I need to put something in the <web> section to bind. Not sure
>> > what to put.
>> >
>> >
>> > On Fri, Aug 21, 2020 at 10:23 AM Justin Bertram <jb...@apache.org>
>> wrote:
>> >
>> >> You're using Artemis right? Artemis doesn't have that config file. The
>> >> embedded web server is configured in bootstrap.xml. Can you paste your
>> >> bootstrap.xml?
>> >>
>> >>
>> >> Justin
>> >>
>> >> On Fri, Aug 21, 2020 at 9:12 AM Christopher Pisz <
>> >> christopherpisz@gmail.com>
>> >> wrote:
>> >>
>> >>> Either I don't have Jetty installed or I don't know where to find the
>> >>> config file you refer to.
>> >>> Yes I can curl http://localhost:8161
>> >>>
>> >>>
>> >>> On Fri, Aug 21, 2020 at 10:01 AM Jean-Baptiste Onofre <
>> jb@nanthrax.net>
>> >>> wrote:
>> >>>
>> >>>> Hi,
>> >>>>
>> >>>> Can you check that you have 0.0.0.0 for jettyPort/host in
>> >> conf/jetty.xml
>> >>> ?
>> >>>>
>> >>>> Are you able to access the port locally using curl
>> >>>> http://localhost:8161/admin <http://localhost:8161/admin> for
>> >> instance ?
>> >>>>
>> >>>> Regards
>> >>>> JB
>> >>>>
>> >>>>> Le 21 août 2020 à 15:54, Christopher Pisz <
>> christopherpisz@gmail.com
>> >>>
>> >>> a
>> >>>> écrit :
>> >>>>>
>> >>>>> I really want to be able to access the web console remotely for my
>> >>>>> development testing.
>> >>>>>
>> >>>>> I read this:
>> >>>>>
>> >>>>
>> >>>
>> >>
>> https://activemq.apache.org/components/artemis/documentation/latest/management-console.html
>> >>>>>
>> >>>>> and it took me to this:
>> >>>>> https://jolokia.org/reference/html/security.html
>> >>>>>
>> >>>>> I created a file called etc/jolokia-access.xml and I put:
>> >>>>>
>> >>>>> <remote>
>> >>>>> <host>localhost</host>
>> >>>>> <host>ip that showed in ifconfig under ppp0</host>
>> >>>>> </remote>
>> >>>>>
>> >>>>>
>> >>>>> I also opened port 8161 in the firewall.
>> >>>>>
>> >>>>> However, when I open a browser and put in
>> >>> http://machine.domain.com:8161
>> >>>> I
>> >>>>> got connection refused.
>> >>>>>
>> >>>>> I can bring up the console locally if someone goes to the machine.
>> >>>>> People onsite can ssh -X and get firefox working and then bring it
>> up
>> >>>>> locally. I cannot SSH -X firefox for whatever reason, it is
>> >> completely
>> >>>>> unresponsive, which is why I wanted to configure it somehow to just
>> >> let
>> >>>> me
>> >>>>> use my own browser and access the page.
>> >>>>>
>> >>>>> Any suggestions?
>> >>>>
>> >>>>
>> >>>
>> >>
>>
>>
Re: remotely access web console
Posted by Christopher Pisz <ch...@gmail.com>.
Hell yes! Thank you so much.
On Fri, Aug 21, 2020 at 11:49 AM Jean-Baptiste Onofre <jb...@nanthrax.net>
wrote:
> Oh sorry, I thought you used ActiveMQ "classic", not Artemis.
>
> About Artemis, you have to use 0.0.0.0 instead of localhost to bind on any
> interface.
>
> Regards
> JB
>
> > Le 21 août 2020 à 16:33, Christopher Pisz <ch...@gmail.com> a
> écrit :
> >
> > <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> > <!--
> > ~ Licensed to the Apache Software Foundation (ASF) under one or more
> > ~ contributor license agreements. See the NOTICE file distributed with
> > ~ this work for additional information regarding copyright ownership.
> > ~ The ASF licenses this file to You under the Apache License, Version
> 2.0
> > ~ (the "License"); you may not use this file except in compliance with
> > ~ the License. You may obtain a copy of the License at
> > ~
> > ~ http://www.apache.org/licenses/LICENSE-2.0
> > ~
> > ~ Unless required by applicable law or agreed to in writing, software
> > ~ distributed under the License is distributed on an "AS IS" BASIS,
> > ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
> implied.
> > ~ See the License for the specific language governing permissions and
> > ~ limitations under the License.
> > -->
> >
> > <broker xmlns="http://activemq.org/schema">
> >
> > <jaas-security domain="activemq"/>
> >
> > <!-- artemis.URI.instance is parsed from artemis.instance by the CLI
> > startup.
> > This is to avoid situations where you could have spaces or special
> > characters on this URI -->
> > <server configuration="file:/var/lib/testbroker/etc//broker.xml"/>
> >
> > <!-- The web server is only bound to localhost by default -->
> > <web bind="http://localhost:8161" path="web">
> > <app url="activemq-branding" war="activemq-branding.war"/>
> > <app url="artemis-plugin" war="artemis-plugin.war"/>
> > <app url="console" war="console.war"/>
> > </web>
> >
> >
> > </broker>
> >
> > I imagine I need to put something in the <web> section to bind. Not sure
> > what to put.
> >
> >
> > On Fri, Aug 21, 2020 at 10:23 AM Justin Bertram <jb...@apache.org>
> wrote:
> >
> >> You're using Artemis right? Artemis doesn't have that config file. The
> >> embedded web server is configured in bootstrap.xml. Can you paste your
> >> bootstrap.xml?
> >>
> >>
> >> Justin
> >>
> >> On Fri, Aug 21, 2020 at 9:12 AM Christopher Pisz <
> >> christopherpisz@gmail.com>
> >> wrote:
> >>
> >>> Either I don't have Jetty installed or I don't know where to find the
> >>> config file you refer to.
> >>> Yes I can curl http://localhost:8161
> >>>
> >>>
> >>> On Fri, Aug 21, 2020 at 10:01 AM Jean-Baptiste Onofre <jb@nanthrax.net
> >
> >>> wrote:
> >>>
> >>>> Hi,
> >>>>
> >>>> Can you check that you have 0.0.0.0 for jettyPort/host in
> >> conf/jetty.xml
> >>> ?
> >>>>
> >>>> Are you able to access the port locally using curl
> >>>> http://localhost:8161/admin <http://localhost:8161/admin> for
> >> instance ?
> >>>>
> >>>> Regards
> >>>> JB
> >>>>
> >>>>> Le 21 août 2020 à 15:54, Christopher Pisz <christopherpisz@gmail.com
> >>>
> >>> a
> >>>> écrit :
> >>>>>
> >>>>> I really want to be able to access the web console remotely for my
> >>>>> development testing.
> >>>>>
> >>>>> I read this:
> >>>>>
> >>>>
> >>>
> >>
> https://activemq.apache.org/components/artemis/documentation/latest/management-console.html
> >>>>>
> >>>>> and it took me to this:
> >>>>> https://jolokia.org/reference/html/security.html
> >>>>>
> >>>>> I created a file called etc/jolokia-access.xml and I put:
> >>>>>
> >>>>> <remote>
> >>>>> <host>localhost</host>
> >>>>> <host>ip that showed in ifconfig under ppp0</host>
> >>>>> </remote>
> >>>>>
> >>>>>
> >>>>> I also opened port 8161 in the firewall.
> >>>>>
> >>>>> However, when I open a browser and put in
> >>> http://machine.domain.com:8161
> >>>> I
> >>>>> got connection refused.
> >>>>>
> >>>>> I can bring up the console locally if someone goes to the machine.
> >>>>> People onsite can ssh -X and get firefox working and then bring it up
> >>>>> locally. I cannot SSH -X firefox for whatever reason, it is
> >> completely
> >>>>> unresponsive, which is why I wanted to configure it somehow to just
> >> let
> >>>> me
> >>>>> use my own browser and access the page.
> >>>>>
> >>>>> Any suggestions?
> >>>>
> >>>>
> >>>
> >>
>
>
Re: remotely access web console
Posted by Jean-Baptiste Onofre <jb...@nanthrax.net>.
Oh sorry, I thought you used ActiveMQ "classic", not Artemis.
About Artemis, you have to use 0.0.0.0 instead of localhost to bind on any interface.
Regards
JB
> Le 21 août 2020 à 16:33, Christopher Pisz <ch...@gmail.com> a écrit :
>
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> <!--
> ~ Licensed to the Apache Software Foundation (ASF) under one or more
> ~ contributor license agreements. See the NOTICE file distributed with
> ~ this work for additional information regarding copyright ownership.
> ~ The ASF licenses this file to You under the Apache License, Version 2.0
> ~ (the "License"); you may not use this file except in compliance with
> ~ the License. You may obtain a copy of the License at
> ~
> ~ http://www.apache.org/licenses/LICENSE-2.0
> ~
> ~ Unless required by applicable law or agreed to in writing, software
> ~ distributed under the License is distributed on an "AS IS" BASIS,
> ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> ~ See the License for the specific language governing permissions and
> ~ limitations under the License.
> -->
>
> <broker xmlns="http://activemq.org/schema">
>
> <jaas-security domain="activemq"/>
>
> <!-- artemis.URI.instance is parsed from artemis.instance by the CLI
> startup.
> This is to avoid situations where you could have spaces or special
> characters on this URI -->
> <server configuration="file:/var/lib/testbroker/etc//broker.xml"/>
>
> <!-- The web server is only bound to localhost by default -->
> <web bind="http://localhost:8161" path="web">
> <app url="activemq-branding" war="activemq-branding.war"/>
> <app url="artemis-plugin" war="artemis-plugin.war"/>
> <app url="console" war="console.war"/>
> </web>
>
>
> </broker>
>
> I imagine I need to put something in the <web> section to bind. Not sure
> what to put.
>
>
> On Fri, Aug 21, 2020 at 10:23 AM Justin Bertram <jb...@apache.org> wrote:
>
>> You're using Artemis right? Artemis doesn't have that config file. The
>> embedded web server is configured in bootstrap.xml. Can you paste your
>> bootstrap.xml?
>>
>>
>> Justin
>>
>> On Fri, Aug 21, 2020 at 9:12 AM Christopher Pisz <
>> christopherpisz@gmail.com>
>> wrote:
>>
>>> Either I don't have Jetty installed or I don't know where to find the
>>> config file you refer to.
>>> Yes I can curl http://localhost:8161
>>>
>>>
>>> On Fri, Aug 21, 2020 at 10:01 AM Jean-Baptiste Onofre <jb...@nanthrax.net>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> Can you check that you have 0.0.0.0 for jettyPort/host in
>> conf/jetty.xml
>>> ?
>>>>
>>>> Are you able to access the port locally using curl
>>>> http://localhost:8161/admin <http://localhost:8161/admin> for
>> instance ?
>>>>
>>>> Regards
>>>> JB
>>>>
>>>>> Le 21 août 2020 à 15:54, Christopher Pisz <christopherpisz@gmail.com
>>>
>>> a
>>>> écrit :
>>>>>
>>>>> I really want to be able to access the web console remotely for my
>>>>> development testing.
>>>>>
>>>>> I read this:
>>>>>
>>>>
>>>
>> https://activemq.apache.org/components/artemis/documentation/latest/management-console.html
>>>>>
>>>>> and it took me to this:
>>>>> https://jolokia.org/reference/html/security.html
>>>>>
>>>>> I created a file called etc/jolokia-access.xml and I put:
>>>>>
>>>>> <remote>
>>>>> <host>localhost</host>
>>>>> <host>ip that showed in ifconfig under ppp0</host>
>>>>> </remote>
>>>>>
>>>>>
>>>>> I also opened port 8161 in the firewall.
>>>>>
>>>>> However, when I open a browser and put in
>>> http://machine.domain.com:8161
>>>> I
>>>>> got connection refused.
>>>>>
>>>>> I can bring up the console locally if someone goes to the machine.
>>>>> People onsite can ssh -X and get firefox working and then bring it up
>>>>> locally. I cannot SSH -X firefox for whatever reason, it is
>> completely
>>>>> unresponsive, which is why I wanted to configure it somehow to just
>> let
>>>> me
>>>>> use my own browser and access the page.
>>>>>
>>>>> Any suggestions?
>>>>
>>>>
>>>
>>
Re: remotely access web console
Posted by Christopher Pisz <ch...@gmail.com>.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<!--
~ Licensed to the Apache Software Foundation (ASF) under one or more
~ contributor license agreements. See the NOTICE file distributed with
~ this work for additional information regarding copyright ownership.
~ The ASF licenses this file to You under the Apache License, Version 2.0
~ (the "License"); you may not use this file except in compliance with
~ the License. You may obtain a copy of the License at
~
~ http://www.apache.org/licenses/LICENSE-2.0
~
~ Unless required by applicable law or agreed to in writing, software
~ distributed under the License is distributed on an "AS IS" BASIS,
~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
~ See the License for the specific language governing permissions and
~ limitations under the License.
-->
<broker xmlns="http://activemq.org/schema">
<jaas-security domain="activemq"/>
<!-- artemis.URI.instance is parsed from artemis.instance by the CLI
startup.
This is to avoid situations where you could have spaces or special
characters on this URI -->
<server configuration="file:/var/lib/testbroker/etc//broker.xml"/>
<!-- The web server is only bound to localhost by default -->
<web bind="http://localhost:8161" path="web">
<app url="activemq-branding" war="activemq-branding.war"/>
<app url="artemis-plugin" war="artemis-plugin.war"/>
<app url="console" war="console.war"/>
</web>
</broker>
I imagine I need to put something in the <web> section to bind. Not sure
what to put.
On Fri, Aug 21, 2020 at 10:23 AM Justin Bertram <jb...@apache.org> wrote:
> You're using Artemis right? Artemis doesn't have that config file. The
> embedded web server is configured in bootstrap.xml. Can you paste your
> bootstrap.xml?
>
>
> Justin
>
> On Fri, Aug 21, 2020 at 9:12 AM Christopher Pisz <
> christopherpisz@gmail.com>
> wrote:
>
> > Either I don't have Jetty installed or I don't know where to find the
> > config file you refer to.
> > Yes I can curl http://localhost:8161
> >
> >
> > On Fri, Aug 21, 2020 at 10:01 AM Jean-Baptiste Onofre <jb...@nanthrax.net>
> > wrote:
> >
> > > Hi,
> > >
> > > Can you check that you have 0.0.0.0 for jettyPort/host in
> conf/jetty.xml
> > ?
> > >
> > > Are you able to access the port locally using curl
> > > http://localhost:8161/admin <http://localhost:8161/admin> for
> instance ?
> > >
> > > Regards
> > > JB
> > >
> > > > Le 21 août 2020 à 15:54, Christopher Pisz <christopherpisz@gmail.com
> >
> > a
> > > écrit :
> > > >
> > > > I really want to be able to access the web console remotely for my
> > > > development testing.
> > > >
> > > > I read this:
> > > >
> > >
> >
> https://activemq.apache.org/components/artemis/documentation/latest/management-console.html
> > > >
> > > > and it took me to this:
> > > > https://jolokia.org/reference/html/security.html
> > > >
> > > > I created a file called etc/jolokia-access.xml and I put:
> > > >
> > > > <remote>
> > > > <host>localhost</host>
> > > > <host>ip that showed in ifconfig under ppp0</host>
> > > > </remote>
> > > >
> > > >
> > > > I also opened port 8161 in the firewall.
> > > >
> > > > However, when I open a browser and put in
> > http://machine.domain.com:8161
> > > I
> > > > got connection refused.
> > > >
> > > > I can bring up the console locally if someone goes to the machine.
> > > > People onsite can ssh -X and get firefox working and then bring it up
> > > > locally. I cannot SSH -X firefox for whatever reason, it is
> completely
> > > > unresponsive, which is why I wanted to configure it somehow to just
> let
> > > me
> > > > use my own browser and access the page.
> > > >
> > > > Any suggestions?
> > >
> > >
> >
>
Re: remotely access web console
Posted by Justin Bertram <jb...@apache.org>.
You're using Artemis right? Artemis doesn't have that config file. The
embedded web server is configured in bootstrap.xml. Can you paste your
bootstrap.xml?
Justin
On Fri, Aug 21, 2020 at 9:12 AM Christopher Pisz <ch...@gmail.com>
wrote:
> Either I don't have Jetty installed or I don't know where to find the
> config file you refer to.
> Yes I can curl http://localhost:8161
>
>
> On Fri, Aug 21, 2020 at 10:01 AM Jean-Baptiste Onofre <jb...@nanthrax.net>
> wrote:
>
> > Hi,
> >
> > Can you check that you have 0.0.0.0 for jettyPort/host in conf/jetty.xml
> ?
> >
> > Are you able to access the port locally using curl
> > http://localhost:8161/admin <http://localhost:8161/admin> for instance ?
> >
> > Regards
> > JB
> >
> > > Le 21 août 2020 à 15:54, Christopher Pisz <ch...@gmail.com>
> a
> > écrit :
> > >
> > > I really want to be able to access the web console remotely for my
> > > development testing.
> > >
> > > I read this:
> > >
> >
> https://activemq.apache.org/components/artemis/documentation/latest/management-console.html
> > >
> > > and it took me to this:
> > > https://jolokia.org/reference/html/security.html
> > >
> > > I created a file called etc/jolokia-access.xml and I put:
> > >
> > > <remote>
> > > <host>localhost</host>
> > > <host>ip that showed in ifconfig under ppp0</host>
> > > </remote>
> > >
> > >
> > > I also opened port 8161 in the firewall.
> > >
> > > However, when I open a browser and put in
> http://machine.domain.com:8161
> > I
> > > got connection refused.
> > >
> > > I can bring up the console locally if someone goes to the machine.
> > > People onsite can ssh -X and get firefox working and then bring it up
> > > locally. I cannot SSH -X firefox for whatever reason, it is completely
> > > unresponsive, which is why I wanted to configure it somehow to just let
> > me
> > > use my own browser and access the page.
> > >
> > > Any suggestions?
> >
> >
>
Re: remotely access web console
Posted by Christopher Pisz <ch...@gmail.com>.
Either I don't have Jetty installed or I don't know where to find the
config file you refer to.
Yes I can curl http://localhost:8161
On Fri, Aug 21, 2020 at 10:01 AM Jean-Baptiste Onofre <jb...@nanthrax.net>
wrote:
> Hi,
>
> Can you check that you have 0.0.0.0 for jettyPort/host in conf/jetty.xml ?
>
> Are you able to access the port locally using curl
> http://localhost:8161/admin <http://localhost:8161/admin> for instance ?
>
> Regards
> JB
>
> > Le 21 août 2020 à 15:54, Christopher Pisz <ch...@gmail.com> a
> écrit :
> >
> > I really want to be able to access the web console remotely for my
> > development testing.
> >
> > I read this:
> >
> https://activemq.apache.org/components/artemis/documentation/latest/management-console.html
> >
> > and it took me to this:
> > https://jolokia.org/reference/html/security.html
> >
> > I created a file called etc/jolokia-access.xml and I put:
> >
> > <remote>
> > <host>localhost</host>
> > <host>ip that showed in ifconfig under ppp0</host>
> > </remote>
> >
> >
> > I also opened port 8161 in the firewall.
> >
> > However, when I open a browser and put in http://machine.domain.com:8161
> I
> > got connection refused.
> >
> > I can bring up the console locally if someone goes to the machine.
> > People onsite can ssh -X and get firefox working and then bring it up
> > locally. I cannot SSH -X firefox for whatever reason, it is completely
> > unresponsive, which is why I wanted to configure it somehow to just let
> me
> > use my own browser and access the page.
> >
> > Any suggestions?
>
>
Re: remotely access web console
Posted by Jean-Baptiste Onofre <jb...@nanthrax.net>.
Hi,
Can you check that you have 0.0.0.0 for jettyPort/host in conf/jetty.xml ?
Are you able to access the port locally using curl http://localhost:8161/admin <http://localhost:8161/admin> for instance ?
Regards
JB
> Le 21 août 2020 à 15:54, Christopher Pisz <ch...@gmail.com> a écrit :
>
> I really want to be able to access the web console remotely for my
> development testing.
>
> I read this:
> https://activemq.apache.org/components/artemis/documentation/latest/management-console.html
>
> and it took me to this:
> https://jolokia.org/reference/html/security.html
>
> I created a file called etc/jolokia-access.xml and I put:
>
> <remote>
> <host>localhost</host>
> <host>ip that showed in ifconfig under ppp0</host>
> </remote>
>
>
> I also opened port 8161 in the firewall.
>
> However, when I open a browser and put in http://machine.domain.com:8161 I
> got connection refused.
>
> I can bring up the console locally if someone goes to the machine.
> People onsite can ssh -X and get firefox working and then bring it up
> locally. I cannot SSH -X firefox for whatever reason, it is completely
> unresponsive, which is why I wanted to configure it somehow to just let me
> use my own browser and access the page.
>
> Any suggestions?