It's been about 8-10 years since I last used ISPC and there have been a few changes since then. You guys have done a great job! I've added a new website (example.tld) and then created a vhost subdomain sub.example.tld outside the example.tld /web folder using /sub/ (not /web/sub). Because of Cloudflare I've created the ssh and sftp subdomains (not vhost) for example.tld. All that works as expected. So far, life is good. Now, because of Cloudflare, I've come up against a need to have a subdomain under example.tld to point to suddomain "sub". Is this possible (I'm assuming it is)? The part that confuses me is the redirect path. I'm not sure what path I need to make the redirect work. Life is starting to not be so good. LOL In the path tree below, what would my redirect path be? |-- /client2 .....|-- /web4 ..........|-- /sub <-- where subdomain resides ..........|-- /web <--where example.tld resides Paths I've tried that have failed: /var/www/clients/client2/web4/sub /www/clients/client2/web4/sub /clients/client2/web4/sub I've found several examples on here and in the manual, but got negative results. Maybe I'm chasing something that does not work? Any help would sure be appreciated!
If you created a vhost subdomain, then you do not need a redirect as sub.example.tld already points to the folder /www/clients/client2/web4/sub No need to enter anything on the redirect tab for that.
I have a software developer who has a website on the subdomain "test" who's software accesses a repo folder inside /test via apt-get for updating the software. Cloudflare is interfering with that access unless the subdomain's proxy is turned off. I had the same issue with the main domain while using SFTP. I created a subdomain "sftp" to bypass Cloudflare's proxy on the main domain. I need to do something similar with the subdomain. Basically, I'm looking to create another door to access /test that isn't proxied by Cloudflare. Can it be done using a (not vhost) subdomain to point to /test or to a folder inside /test? I'd prefer to not leave the proxy turned off for the subdomain. I'd prefer not to use Cloudflare at all, but because of the amount of bad traffic hitting both sites I have to use CF.
SFTP is not domain name dependent, only the username you use for login matters, you can use any IP, the domain name, any subdomain pointing to the server, or the server hostname to connect with SFTP. So creating a website as a vhost subdomain for SFTP is not needed.
This isn't about SFTP or my main domain. SFTP did not work using IP or the server name - that is the reason I created a non-vhost subdomain. I did not create a vhost for SFTP. I was using that as an example for what I'm wanting to do to have access to a folder inside vhost subdomain /test. My question is, as it has been from the first post... Can I use a non-vhost subdomain to access a folder in a vhost subdomain? If I can, what is the file path?
That is quite strange, why didn't you fix that first? I think it should normally work just fine. From what I gathered above, @till said yes, but nothing is to be entered in the path field. Now I started to think your problem is just sftp for the subdomain, not creating a non-vhost subdomain, am I wrong?
SFTP was working just fine on my domain until I started using Cloudflare. Same with SSH. Cloudflare was interfering with SFTP and SSH, which I was able to fix by using a non-vhost subdomain and keeping CF's proxy turned off for that non-vhost subdomain. The only reason I've even mentioned SFTP and SSH is because that was an example of how I was able to work around Cloudflare interfering with SFTP and SSH, and I was wanting to do the same thing on my vhost subdomain. Now, lets forget all about SFTP and SSH and my main domain. Cloudflare is also interfering with access to my vhost subdomain using APT-GET to update some software packages. Right now the only way I can access my vhost subdomain using APT-GET is to turn off Cloudflare's proxy for that vhost subdomain. Till's answer did not answer my question. His answer stated /sub was in /web4 and I needed to do nothing more. /sub is not in /web4. /sub is up one level in /sub. |-- /client2 .....|-- /web4 ..........|-- /sub/some_folder <-- where subdomain resides (/sub is not in /web) ..........|-- /web/my_website <--where example.tld resides I'm trying to find out if a non-vhost subdomain can be used to access a vhost subdomain that is not in the /web folder (see folder tree directly above). If it can, what would the path be. Each path I've tried does not work, but maybe there might be a path I have not found that will work.
Sub is there here you add it. If you enter 'sub' as folder name, then its in web4, if yiu enter web/sub as folder name, then its in web4/web/sub
Thanks, Till! That was just enough info to get me going in the right direction! After trying a few variants of your example path, and using https:// test.example.tld to test, it would always send me to example.tld and not to sub.example.tld. I then changed my thinking for the redirect path. I switched to a URL https:// sub.example.tld/repo as the redirect path. That worked! Now when using https:// test.example.tld, I'm sent to https:// sub.example.tld/repo - even with Cloudflare's proxy enable for sub.domain.tld. (Before starting this topic I tried using an URL but it did not work. I don't know what I did different this time compared to before.) I still need to do a software test with APT-GET to see if that works, but that will be much later today. I'll report back with my results.
I was told by the software dev that the testing results came back positive, so the above URL path was the one that worked for my use case.
