Tpye the following into commandline:

/etc/rc.d/rc.netaddress.down; /etc/rc.d/rc.netaddress.up

Which logs out the following on screen:

Setting up firewall
Restarting DNS proxy
Bringing up interface aliases (if they exist)
Register: Already registered
got my.SmoothWall system info with id [xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx]
Setting up firewall
Starting traffic stats collector
Setting DMZ pinholes
Setting up advanced networking features
Setting up IP block
Setting external access rules
Setting up outgoing filter
Setting up timed access rules

Simplified steps to add a second hard drive to a Debian server running Proxmox.

Firstly physically install the Hard Drive in the server chassis.

Startup the server and run the following from commandline to find the device name for the disk:

fdisk -l

This should return something similar to this:

Disk /dev/sda: 21.4 GB, 21474836480 bytes
255 heads, 63 sectors/track, 2610 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 2517 20217771 83 Linux
/dev/sda2 2518 2610 747022+ 5 Extended
/dev/sda5 2518 2610 746991 82 Linux swap / Solaris

Disk /dev/sdb: 32.2 GB, 32212254720 bytes
255 heads, 63 sectors/track, 3916 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sdb doesn't contain a valid partition table

If it is the first new disk you have added it will more than likely be /dev/sdb as the device name.

Now we partition the disk:

cfdisk /dev/sdb

Select the following options:

• New > Primary > Enter (use the size in MB already specified)
• Write
• Quit

Now we format the disk to the ext3 filesystem:

mkfs.ext3 /dev/sdb1 

Mount the drive to a new folder:

mkdir /mnt/backups
mount -t ext3 /dev/sdb1 /mnt/backups 

Lastly we add the disk to /etc/fstab so it auto-mounts when we reboot the machine:

 
/dev/sdb1 /mnt/backups ext3 defaults,errors=remount-ro 0 1 

That’s your drive mounted and ready to be added as backup storage in Proxmox.

To test: reboot the machine and confirm that the drive is still mounted.

Simple but effective command:

 
scp -P 2222 file.tar username@www.myserver.com:/pathto/remotedirectory

Few tips to setup the admin section.

OpenVPN hostname/IP setup (you can use NOIP)

Server Network Settings

Routing/Subnets  (allow user to see all other machines on the remote network)

Routing/Subnet OpenVPN AS

Everything else I left as default.

So you install OpenVPN-AS via the tutorial located here –

OpenVPN Acess Server Install Debian + Proxmox

Now when you login to the admin console and click “Start Server” you get the following error:

iptables service not started because of error (SVC_RUN_EXCEPT)

This indicates that the IP tables service isn’t running on your VM. To fix the error carry out the following:

Stop the VM from your proxmox host server:

vzctl stop 101

Make the iptables state and nat modules accessible to containers.

vim /etc/vz/vz.conf

Add “ipt_state iptable_nat” to the end of the list of IPTABLES modules

vim /etc/vz/vz.conf

vz.conf

Allow the container to open the TUN/TAP interface.  These steps specifically affect container ID 101:

vzctl set 101 --devices c:10:200:rw --save

vzctl set 101 --capability net_admin:on --save 

These kernel modules and commands should be ran/installed on the host node before the container is started:

modprobe ipt_mark

modprobe ipt_MARK

modprobe tun

Now start the container:

vzctl start 101

After starting the container run these commands on the host node:

vzctl exec 101 mkdir -p /dev/net

vzctl exec 101 mknod /dev/net/tun c 10 200

vzctl exec 101 chmod 600 /dev/net/tun

Now reboot the host machine, login to OpenVPN admin and start theOpenVPN server. Hopefully all should be working well.