proxmox v3 url forwarding

[informant]

Hi all,

in v2 the url was forwarding to ip:8006 if we use http://ip or https://ip only.
in v3 it´s doesn´t work,.

how we can activate autoforward or use a subdomain with autoforward to proxmox webinterface url/port?

please help. thanks

regards

 

[tin]

Well that explains why I couldn't connect to my host after it upgraded... I thought it was the Rube Goldberg remote access setup I was using. After reading this, amazingly I was able to connect again

Any reason for this change?

 

[dietmar]

how we can activate autoforward or use a subdomain with autoforward to proxmox webinterface url/port?

We removed that functionality in 3.0.

 

[tom]

see also http://forum.proxmox.com/threads/13964-Proxmox-3-0-web-ui-on-port-443-instead-of-8006

 

[informant]

Hi,

thanks for answer.

Why do you remove more and more good features. 1st remove incremental backups and than a simple port forwarding?


I have a question to the iptables post:

if we use
iptables -t nat -I PREROUTING -d <server ip> -p tcp --dport 443 -j DNAT --to-destination <server ip>:8006
its works, if we start webinterface with https://...

but if we use http:// it´s doenst work

we have add following iptablerule

iptables -t nat -A PREROUTING -d <server ip> -p tcp --dport 80 -j REDIRECT --to-ports 443
or
iptables -t nat -A PREROUTING -d <server ip> -p tcp --dport 80 -j DNAT --to-destination <server ip>:443

but this doesn´t work.

do you have a idea, please?


regards

 

[tin]

You really need a (simple) web server to achieve the redirect if you want it to work from http:// to the correct URL. Port forwarding will only work for HTTPS requests since it's a different protocol.

 

[informant]

Hm,

ok, not so good. Thanks for answer.

regards

 

[mo_]

if you dont like to use bookmarks - setting up a tiny redirect webserver like lighttpd or nweb is fairly straight forward

 

[PigLover]

Wonder if you might explain why you removed it? A security issue? Customers asking you to remove it? Something else less obvious?

If you'd help people understand why then at least they'd know what benefit they are undoing when they try to put it back.

 

[dietmar]

Wonder if you might explain why you removed it? A security issue? Customers asking you to remove it? Something else less obvious?

We implemented our own web server (pveproxy), and so far we had no time to implement that feature.

 

[informant]

Hi, do iptables on host are not saveing after restart? well after restart the entry is not set.

regards

 

[mo_]

no they dont. iptables-save <filename> will save your current rules to a file and iptables-restore <file> will load rules from a file. you need an init script that does both things on boot/shutdown. a simple version for that can be found here: http://www.debian-administration.org/articles/445 (this does not save your current rules, but it will always reload rules on boot that you have saved manually)

 

[informant]

ok, nice, thanks @mo_