Subdomain proxy directive is hidden

The <script> element just after the hidden proxy field shows:

Code:

    var webId = jQuery('input[name="id"]').val();
    adjustForm();
       
    function adjustForm(){
        jQuery.getJSON('sites/ajax_get_json.php'+ '?' + Math.round(new Date().getTime()), {web_id : webId, type : "getredirecttype"}, function(data) {
            if(data.redirecttype == "proxy"){
                jQuery('.proxy').show();
            } else {
                jQuery('.proxy').hide();
            }
        });
    }

So it seems you would need to edit the main website, under Redirect select "proxy" as the type, and I have no idea what you'd need in Redirect Path at that point, but ... a step closer?

 

You should create it as a separate site instead of a subdomain iirc.

 

Or use a vhost subdomain.

 

There is a setting to enable vhost subdomains/alias domains, I would guess in main config, but can't check at the moment.

 

Do you use Apache or Nginx web server and which ISPConfig version do you use?

 

Go to the redirect tab and set the redirect type to 'proxy' there, then go back to the options tab to see if the field shows up.

 

It is not a bug, you were using a regular subdomain, which just add a ServerAlias to the vhost file; you can use a vhost subdomain to configure that different than the main website.

 

Some days it sure feels that way.

Re-checking the above, indeed, the webId that causes the proxy field to hide is that of the subdomain, I made a mistake in looking that up the first time; so setting the parent website to 'proxy' is not a means to have the proxy field appear on the subdomain options.

The other two solutions mentioned, to create the subdomain as a website itself, or to use a vhost subdomain, do allow me to select 'proxy' as a redirect type.

I've not found anywhere that says invalid domain while doing this, though there is a "Domain is empty." message once you access the Options tab on a subdomain, I'm guessing that's what you are referring to. That is indeed a bug.

As to allowing 'proxy' as an option in the non-vhost subdomain settings, I don't know if there's a technical reason it is not allowed, or simply was an omission when that was implemented. That would require some research/testing.