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

Duy Dao commented on ARTEMIS-2864:
----------------------------------

Hi [~jbertram] ,

thanks for getting in touch with me & sorry for the bad description:

The steps to reproduce this error on my client is:
 * Open the web console page
 * Enter the login information & press login
 * I get redirected to the login page (no error notification)
 * I see "403 Forbidden" responses in the Dev Console (see screenshot)

I've tried to clear/disable the cache and it has no effect. What does work is:
 * Change the domain (e.g. IP instead of localhost)
 * Change the port (e.g. 8162 instead of 8161)
 * Use a private window

I'm pretty sure the problem is on my end, and I just wanted to document the 
workaround in case someone stumbles on the same error. Please feel free to 
close this issue :)

 

> Firefox can't open WebConsole using localhost
> ---------------------------------------------
>
>                 Key: ARTEMIS-2864
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2864
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Web Console
>    Affects Versions: 2.14.0
>         Environment: * macOS 10.15.2
>  * Firefox 78.0.2
>  * Works on Chrome 84
>            Reporter: Duy Dao
>            Priority: Minor
>         Attachments: Bildschirmfoto 2020-08-03 um 20.38.39.png
>
>
> I can't open the Web Console on a fresh broker using the default config. 
> After a successfull login on http://localhost:8161, I get 403 (Forbidden) on 
> the jolokia endpoints.
> This only happens on Firefox 78.0.2 (macOS), it works when I use Chrome 84 or 
> when I use the IP instead of localhost (e.g. http://127.0.0.1:8161 after 
> modifying the jolokia-access.xml)
> As a workaround, I can use Chrome instead of Firefox or the IP instead of 
> localhost.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to