# \[resolved\] Cannot get on web UI remotely (Centos 7 and opennebula 4.12)

**URL:** https://forum.opennebula.io/t/resolved-cannot-get-on-web-ui-remotely-centos-7-and-opennebula-4-12/424
**Category:** Product Support
**Created:** [March 15, 2015, 5:54pm UTC](https://forum.opennebula.io/t/resolved-cannot-get-on-web-ui-remotely-centos-7-and-opennebula-4-12/424 "2015-03-15T17:54:41Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![adewolf](https://avatars.discourse-cdn.com/v4/letter/a/8edcca/32.png) [@adewolf](https://forum.opennebula.io/u/adewolf)
#### Post date: [March 15, 2015, 5:54pm UTC](https://forum.opennebula.io/t/resolved-cannot-get-on-web-ui-remotely-centos-7-and-opennebula-4-12/424/1 "2015-03-15T17:54:41Z")

</div>

Hello all:  
I got OpenNebula 4.12 on Centos 4.12. I can get to the web ui on the local host only.  
Here is /etc/open/sunstone-server.conf:  
################################################################################

# Server Configuration

################################################################################

# Directory to store temp files when uploading images

# 

:tmpdir: /var/tmp

# OpenNebula sever contact information

# 

:one\_xmlrpc: [http://localhost:2633/RPC2](http://localhost:2633/RPC2)

# Server Configuration

# 

:host: 0.0.0.0  
:port: 9869

# Place where to store sessions, this value can be memory or memcache

# Use memcache when starting multiple server processes, for example,

# with passenger

# 

# NOTE. memcache needs a separate memcached server to be configured. Refer

# to memcached documentation to configure the server.

:sessions: memory

# Memcache configuration

:memcache\_host: localhost  
:memcache\_port: 11211  
:memcache\_namespace: opennebula.sunstone

################################################################################

# Log

################################################################################

# Log debug level

# 0 = ERROR, 1 = WARNING, 2 = INFO, 3 = DEBUG

# 

:debug\_level: 3

################################################################################

# Auth

################################################################################

# Authentication driver for incomming requests

# sunstone, for OpenNebula’s user-password scheme

# x509, for x509 certificates based authentication

# opennebula, the authentication will be done by the opennebula core using the

# driver defined for the user

# 

:auth: opennebula

# Authentication driver to communicate with OpenNebula core

# cipher, for symmetric cipher encryption of tokens

# x509, for x509 certificate encryption of tokens

# 

:core\_auth: cipher

# For LDAP auth. Encode credentials sent to OpenNebula. Turns espaces into %20.

# This only works with “opennebula” auth.

# 

#:encode\_user\_password: true

################################################################################

# UI Settings

################################################################################

# :vnc\_proxy\_

# port: port where the vnc proxy will listen

# support\_wss: no | yes | only. For yes and only, provide path to

# cert and key. “yes” means both ws and wss connections will be

# supported.

# vnc\_proxy\_cert: Certificate to encrypt wss connections.

# vnc\_proxy\_key: Key for wss connections. Only necessary if not included in cert.

# vnc\_proxy\_ipv6: Enable ipv6 support for novnc-server

:vnc\_proxy\_port: 29876  
:vnc\_proxy\_support\_wss: no  
:vnc\_proxy\_cert:  
:vnc\_proxy\_key:  
:vnc\_proxy\_ipv6: false

# Default language setting

:lang: en\_US

# Default table order

:table\_order: desc

################################################################################

# Marketplace

################################################################################

# Marketplace username and password

# If no credentials are provided, an anonymous client will be used

# 

#:marketplace\_username:  
#:marketplace\_password:

################################################################################

# OneFlow

################################################################################

# OneFlow endpoint

# 

:oneflow\_server: [http://localhost:2474/](http://localhost:2474/)

################################################################################

# Default instance types for the cloud view

################################################################################

# 

# These types are presented in the cloud view to customize VM Templates. Each

# type is defined by:

# name: the name of the type

# cpu: capacity allocated to the VM for scheduling purposes

# vcpu: number of cores

# memory: in MB for the VM

# description: to help the user pick one, it may include purpose or price.

:instance\_types:  
- :name: small-x1  
:cpu: 1  
:vcpu: 1  
:memory: 128  
:description: Very small instance for testing purposes  
- :name: small-x2  
:cpu: 2  
:vcpu: 2  
:memory: 512  
:description: Small instance for testing multi-core applications  
- :name: medium-x2  
:cpu: 2  
:vcpu: 2  
:memory: 1024  
:description: General purpose instance for low-load servers  
- :name: medium-x4  
:cpu: 4  
:vcpu: 4  
:memory: 2048  
:description: General purpose instance for medium-load servers  
- :name: large-x4  
:cpu: 4  
:vcpu: 4  
:memory: 4096  
:description: General purpose instance for servers  
- :name: large-x8  
:cpu: 8  
:vcpu: 8  
:memory: 8192  
:description: General purpose instance for high-load servers

################################################################################

# Routes

################################################################################

# Array of files containing ruby code to extend the default sunstone-server

# routes. These files must be placed inside the custom\_routes directory

# in the sunstone root dir (/usr/lib/one/sunstone/routes)

# 

# Example:

# $ ls /usr/lib/one/sunstone/routes

# custom.rb other.rb

# 

# $ cat /usr/lib/one/sunstone/routes/example.rb

# get ‘/custom’ do

# body “It works”

# end

# 

#:routes:

# - custom

# - other

:routes:  
- oneflow  
- vcenter  
- support

---

<div class="post-metadata">

### Author: ![adewolf](https://avatars.discourse-cdn.com/v4/letter/a/8edcca/32.png) [@adewolf](https://forum.opennebula.io/u/adewolf)
#### Post date: [March 15, 2015, 7:13pm UTC](https://forum.opennebula.io/t/resolved-cannot-get-on-web-ui-remotely-centos-7-and-opennebula-4-12/424/2 "2015-03-15T19:13:52Z")

</div>

OK when I reload iptables it works. How do I make this persistant.

---

<div class="post-metadata">

### Author: ![jdreese](https://avatars.discourse-cdn.com/v4/letter/j/eb8c5e/32.png) [@jdreese](https://forum.opennebula.io/u/jdreese)
#### Post date: [March 16, 2015, 1:13pm UTC](https://forum.opennebula.io/t/resolved-cannot-get-on-web-ui-remotely-centos-7-and-opennebula-4-12/424/3 "2015-03-16T13:13:58Z")

</div>

CentOS 7 uses the firewalld service for its firewall (although iptables can still be used to list firewall info). These commands should permanently open port 9869:

```
firewall-cmd --zone=public --add-port=9869/tcp --permanent
firewall-cmd --reload
```

---

<div class="post-metadata">

### Author: ![adewolf](https://avatars.discourse-cdn.com/v4/letter/a/8edcca/32.png) [@adewolf](https://forum.opennebula.io/u/adewolf)
#### Post date: [March 16, 2015, 8:33pm UTC](https://forum.opennebula.io/t/resolved-cannot-get-on-web-ui-remotely-centos-7-and-opennebula-4-12/424/4 "2015-03-16T20:33:15Z")

</div>

> [@jdreese](#):
>
> firewall-cmd --reload

Thanks that fixed it
