Hello,
I want to install it on my Proxmox server and get the following error message:
setup/questions.sh: line 99: DEFAULT_PUBLIC_IP: unbound variable
I have taken the following steps:
apt update
apt upgrade
git clone --single-branch -b ubuntu_bionic https://github.com/mail-in-box/mailinabox
cd mailinabox/
bash setup/start.shIs there a public IP address ? I am not familiar with Proxmox so I cannot help you other than to ask the obvious … is the script able to see a public IP address??? From the error I would guess not.
yes, I bought the ip extra.
How can I check this?
I don’t really understand how we could reproduce this error. Did you run the BASH script as root (or sudo)?
ifconfig
It should show your internet facing IP as the inet addr
As already written above, I have created a container with Ubuntu 18.04 on my Proxmox server. Then I did apt-get update and apt-get upgrade and apt-get dist-upgrade as root. Thereupon I adjusted my /etc/hosts as follows:
127.0.0.1 localhost.localdomain localhost
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
# --- BEGIN PVE ---
185.xxx.xx.204 box.example.com box
# --- END PVE ---
and this is what my /etc/hostname looks like:
box
Then I have the following steps as root performed:
git clone --single - branch - b ubuntu_bionic https://github.com/mail - in - box / mailinabox
cd mailinabox /
bash setup / start.sh
Output from ifconfig:
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 185.xxx.xx.204 netmask 255.255.255.0 broadcast 185.xxx.xx.255
inet6 fe80::xxxx:xxxx:xxxx:2206 prefixlen 64 scopeid 0x20<link>
ether 52:xx:xx:xx:xx:06 txqueuelen 1000 (Ethernet)
RX packets 10427 bytes 637451 (637.4 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 137 bytes 16771 (16.7 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0I already saw this thread.
The mailinabox/setup/questions.sh has already been changed. Without success.
What if you set the variable, then run setup:
export DEFAULT_PUBLIC_IP=xxx.xxx.xxx.xxx
cd mailinabox/
bash setup/start.sh
where “x” is your IP.
Many Thanks. That solved the problem.
Now I have another problem.
When trying to install mailinabox, I receive the following message at the end:
Waiting for the mail-in-a-box management daemon to start ...
Waiting for the mail-in-a-box management daemon to start ...
Waiting for the mail-in-a-box management daemon to start ...
in a loop
anything in syslog?
cat /var/log/syslog | grep mailinabox
Dec 26 23:55:00 box start[3041]: File "/usr/local/lib/mailinabox/env/lib/python3.6/encodings/ascii.py", line 26, in decode
Dec 26 23:55:00 box systemd[1]: mailinabox.service: Main process exited, code=exited, status=1/FAILURE
Dec 26 23:55:00 box systemd[1]: mailinabox.service: Failed with result 'exit-code'.
Dec 26 23:55:01 box cron[210]: (*system*mailinabox-nightly) RELOAD (/etc/cron.d/mailinabox-nightly)
Dec 27 00:00:34 box systemd[1]: mailinabox.service: Failed to reset devices.list: Operation not permitted
Dec 27 00:00:35 box start[581]: File "/root/mailinabox/management/daemon.py", line 27, in <module>Looks like a permissions issue.
I have created a new container with Ubuntu 14.04 and installed mailinabox, which worked without problems.
Hmm Just curious, did you install anything besides MIAB on the old container?
no, only MIAB nothing else
Nobody has any idea what this could be?
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.