Running website on VM, but cannot access it internally and externally

[GTCG]

Hello

I've been trying to get a Codius server up and running on my Freenas via this guide: https://medium.com/codius/how-to-run-your-own-codius-host-42e13afe1fb2
Freenas is running on a HP Proliant server gen8, with 16 GB of RAM. I am using a virtual machine with CENTOS7 installed on it to set up the codius server.
Setting everything up went fine. I installed the required software, set up my domain and subdomain which I linked to my external IP-address and installed the certificates. I can ping the domain (www.bollius.com) and subdomain (www.codius.bollius.com). So far so good.

The problem is that I cannot access the website (not internal and external)

I SSH'd into my virtual machine and did this:

Code:

 ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group defaul																																							 t qlen 1000
	link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
	inet 127.0.0.1/8 scope host lo
	   valid_lft forever preferred_lft forever
	inet6 ::1/128 scope host
	   valid_lft forever preferred_lft forever
2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP																																							  group default qlen 1000
	link/ether 00:a0:98:39:fa:c8 brd ff:ff:ff:ff:ff:ff
	inet 192.168.0.18/24 brd 192.168.0.255 scope global noprefixroute dynamic en																																							 p0s3
	   valid_lft 72720sec preferred_lft 72720sec
	inet6 fe80::f4cc:574:8fce:fc7e/64 scope link noprefixroute
	   valid_lft forever preferred_lft forever
3: codius0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNO																																							 WN group default qlen 1000
	link/ether a6:0d:e8:4f:ea:40 brd ff:ff:ff:ff:ff:ff
	inet 169.254.77.68/32 scope global codius0
	   valid_lft forever preferred_lft forever
	inet6 fe80::a40d:e8ff:fe4f:ea40/64 scope link
	   valid_lft forever preferred_lft forever

The 3rd interface (codius0) seems to have gotten an APIPA-address, but I don't know why...

and I am wondering if it is caused by a setting in the virtual machine, perhaps firewall or something else which could be blocking traffic?
When setting firewall rules in the VM, do you have to apply the same firewall rules to the NAS as well, or are both machines seen as separate hosts?
Another question which I'm looking into: how can I check wether the VM is in bridged or in NAT-mode? How can I modify this setting?
I can ping and SSH into the VM and NAS.

 

[dlavigne]

Were you able to resolve this?

 

[GTCG]

Were you able to resolve this?

Yes, I was actually. I got everything running in the end. Everything was set up as required and the APIPA-address was actually not a problem.