accessing ihub localhost on virtual box guest from mac host

<p>hi, this is a somewhat complicated set-up:</p>
<p>I installed Linux centOS in VirtualBox (guest) on my MacBook Pro (host).</p>
<p>I installed the iHub trial edition in centOS (v7) and it runs fine, at the address localhost:8700/iportal</p>
<p> </p>
<p>Now I would like to connect to iHub (running in the guest) from Birt Designer Pro (running in the host), so I can publish reports.</p>
<p>I tried to set up a server profile in BirtDesigner but get an error message (connection refused).</p>
<p>How do I solve this?</p>

Find more posts tagged with

Comments

JFreeman

<p>My first guess is the firewall is running on your CentOS installation.</p>
<p> </p>
<p>In CentOS 7.x, you stop the firewall daemon using systemd like this:</p>
<pre class="_prettyXprint _lang-nocode">
systemctl stop firewalld
</pre>
<p>You will need to be root or using sudo to have permission to use systemd to stop processes.</p>
<p>That will quickly help verify if the issue is firewall related.</p>
<p> </p>
<p>If that does not work, can you attach a screenshot of the connection properties you are using in the designer that are being refused?</p>

DQM

<p>hi Jesse, thanks for your quick reply.</p>
<p>I used root and stopped the firewall, but the issue persists.</p>
<p> </p>
<p>screenshot attached.</p>
<p>(BTW, if I use the address "192.168.56.1" instead of "192.168.56.101" I get "connection refused" as error message)</p>

DQM

<p>Just to make sure the host can actually see the guest I ran ifconfig vboxnet0 in the osx terminal.app, and it returned</p>
<p><span style="font-family:Menlo;font-size:11px;">mk$ ifconfig vboxnet0</span></p>
<p style="font-size:11px;font-family:Menlo;">vboxnet0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500</p>
<p style="font-size:11px;font-family:Menlo;">ether 0a:00:27:00:00:00 </p>
<p style="font-size:11px;font-family:Menlo;">inet 192.168.56.1 netmask 0xffffff00 broadcast 192.168.56.255</p>

JFreeman

<p>Thanks for the details and screenshot.</p>
<p>In the Server Profile, change the port to the default of 8000 instead of 8700. This should resolve your issue.</p>
<p> </p>
<p>Port 8700 is the front end web application port and port 8000 is the SOAP port. When the designer publishes files to the iHub it uses the Information Delivery API (IDAPI) which is a SOAP based API that communicates with the iHub on it's SOAP port.</p>

DQM

<p>no joy on port 8000 either.</p>
<p>I stopped the firewall (twice), see:</p>
<div>[root@localhost mark]# systemctl status firewalld -l</div>
<div>firewalld.service - firewalld - dynamic firewall daemon</div>
<div> Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled)</div>
<div> Active: inactive (dead) since Thu 2015-08-20 16:19:37 CEST; 11min ago</div>
<div> Process: 627 ExecStart=/usr/sbin/firewalld --nofork --nopid $FIREWALLD_ARGS (code=exited, status=0/SUCCESS)</div>
<div> Main PID: 627 (code=exited, status=0/SUCCESS)</div>
<div> CGroup: /system.slice/firewalld.service</div>
<div>Aug 20 16:18:53 localhost.localdomain systemd[1]: Started firewalld - dynamic firewall daemon.</div>
<div>Aug 20 16:19:36 localhost.localdomain systemd[1]: Stopping firewalld - dynamic firewall daemon...</div>
<div>Aug 20 16:19:37 localhost.localdomain systemd[1]: Stopped firewalld - dynamic firewall daemon.</div>
<div> </div>
<div>checklist:</div>
<div>In VirtualBox prefs I set up network as "Host-Only" (Adapter gives 192.168.56.1 as IP4 address) and tested if, alternatively, DHCP (set up as server) worked but it didn't).</div>

JFreeman

<p>To confirm, you can connect to the iHub front end from you host machine using <a data-ipb='nomediaparse' href='http://192.168.56.1:8700/iportal'>http://192.168.56.1:8700/iportal</a> ? </p>
<p>On the host machine, can you hit the SOAP wsdl in your web browser at <a data-ipb='nomediaparse' href='http://192.168.56.1:8000/wsdl'>http://192.168.56.1:8000/wsdl</a> ? </p>
<p> </p>
<p>One thing i've noticed is in the screenshot you have the ip address as 192.168.56.101 instead of 192.168.56.1.</p>

DQM

<p>Hi Jesse, no I can't connect from my host to portal or wsdl.</p>
<p>I tried both 192.168.56.101 and 192.168.56.1 (hence the "101" in the screenshot.</p>
<p>192.168.56.1 gave "connection refused" and 192.168.56.101 timed out.</p>
<p>it's very strange.</p>

JFreeman

<p>Okay, well that actually narrows thing down a bit.</p>
<p>I'm guessing at this point it is a network issue getting to the VM.</p>
<p> </p>
<p>Is the virtual box network setup as NAT?</p>
<p>If so, try changing this to a bridged connection. Not sure with virtual box if you will need to reboot or not.</p>
<p> </p>
<p>Once on bridged, it will be assigned an ip address on your actual network from your DHCP server. Then try connecting again.</p>

DQM

<p>Thanks Jesse, will look into that first thing tomorrow</p>

JFreeman

<p>You're welcome.</p>
<p>Let me know how it goes.</p>

DQM

<p>Hi Jesse! It works!</p>
<p>These are steps I took, for future reference:</p>
<p>1) Disabled NAT adapter in VirtualBox settings and enabled Network Bridge Adapter in VirtualBox settings</p>
<p>2) Start Linux centOS in VirtualBox, disabled and stopped firewalld in terminal</p>
<p>3) run ifconfig to get localhost address in terminal</p>
<p>4) entered localhost IP and port 8000 in Birt Designer Pro server settings, running on the host machine</p>
<p>5) published a file and checked it was there in the guest</p>
<p>6) sat back, feeling very good

</p>
<p> </p>
<p>Thanks for your help!</p>

JFreeman

<p>You're welcome.</p>
<p>I'm glad to hear that got it resolved for you.</p>
<p> </p>
<p>Let us know if you have additional questions.</p>