You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Yujie Li (JIRA)" <ji...@apache.org> on 2017/03/14 21:36:41 UTC
[jira] [Comment Edited] (RANGER-1443) Ranger binds to 127.0.0.1
after enabling ssl
[ https://issues.apache.org/jira/browse/RANGER-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15925060#comment-15925060 ]
Yujie Li edited comment on RANGER-1443 at 3/14/17 9:36 PM:
-----------------------------------------------------------
[~pradeep.agrawal]
Hello, please delete this since I mistook the shutdown port as the ssl port. I checked and Ranger doesn't have this issue at all.
Sorry for confusion.
was (Author: yujie.li):
[~pradeep.agrawal]
Hello, please delete this thi since I mistook the shutdown port as the ssl port. I checked and Ranger doesn't have this issue at all.
Sorry for confusion.
> Ranger binds to 127.0.0.1 after enabling ssl
> --------------------------------------------
>
> Key: RANGER-1443
> URL: https://issues.apache.org/jira/browse/RANGER-1443
> Project: Ranger
> Issue Type: Bug
> Components: admin
> Affects Versions: 0.6.2
> Reporter: Yujie Li
> Assignee: Pradeep Agrawal
>
> With http, Ranger binds with 0.0.0.0. But after enabling ssl, it only listens to 127.0.0.1 (localhost). Other IPs can't access to Ranger UI.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)