Re: [users@httpd] port based VirtualHosts ?

[Jason Vas Dias]

Aha ! it is working now - I moved, in /etc/httpd/conf.d, the default
files:
 welcome.conf -> welcome.dir
 manual.conf   -> manual.dir
and then included them from 'Apache.dir', which is included by
both Apache.conf (the *:80 Vhost) and ssl.conf (the *:443 vhost).

So I guess it is because the default, un-vhosted server now has
NO directory entries associated with it, that is has nothing to serve,
so vhost resolution is forced.


On 27/12/2021, Jason Vas Dias  wrote:
> Thanks Eric -
>
>   Yes, it was DocumentRoot, a typo in my email only - sorry .
>
>   I now have ALL site in separate VHosts .
>
>   I put all the default directory entries in conf/httpd.conf into
>   a separate conf.d/Apache.conf :
>
>
>  ServerName $HOST_DNS_NAME:80
>  include conf.d/Apache.dir
>
>
>   And my ssl.conf now does:
>
>   
>  ... # original ssl.conf
>  ServerName $HOST_DNS_NAME:443
>  include conf.d/Apache.dir
>
>
>   And my A & B conf are both (where $PORT is either 2x080 or 1x080)
>   (numbers redacted):
>
> conf.d/A.conf:
> Listen $HOST_DNS_IP:1x080 https
>
> 
>   ServerAdmin ${ME}@localhost
>   ServerName  $HOST_DNS_NAME:1x080
>   DocumentRoot "/opt/A"
>   SSLEngine on
>   SSLCertificateFile/etc/pki/tls/certs/localhost.crt
>   SSLCertificateKeyFile /etc/pki/tls/private/localhost.key
>   ErrorLog"logs/A-error_log"
>   TransferLog "logs/A-access_log"
>   
> Options +ExecCGI +Includes +Indexes +FollowSymLinks
> require all granted
>   
> 
>
> conf.d/B.conf:
>
> Listen $HOST_DNS_IP:2x080 https
>
> 
>   ServerName  $HOST_DNS_NAME:2x080
>   ServerAdmin ${ME}@localhost
>   DocumentRoot "/opt/B"
>   SSLEngine on
>   SSLCertificateFile  /etc/pki/tls/certs/localhost.crt
>   SSLCertificateKeyFile /etc/pki/tls/private/localhost.key
>   ErrorLog "logs/B-error_log"
>   TransferLog "logs/B-access_log"
>   
> Options +ExecCGI +Includes +Indexes +FollowSymLinks
> require all granted
>   
> 
>
> I also created a _default_.conf file containing:
>
> 
> 
>
> httpd starts and httpd -S says :
>
> httpd -S
> VirtualHost configuration:
> *:80 $HOST_DNS_NAME  (/etc/httpd/conf.d/Apache.conf:1)
> *:48080$HOST_DNS_NAME (/etc/httpd/conf.d/B.conf:5)
> *:*  $HOST_DNS_NAME
> (/etc/httpd/conf.d/_default_.conf:1)
> *:60080$HOST_DNS_NAME (/etc/httpd/conf.d/B.conf:5)
> *:443   $HOST_DNS_NAME (/etc/httpd/conf.d/ssl.conf:56)
>
> But still, a request to either $HOST_DNS_NAME:1x080 or
> $HOST_DNS_NAME:2x080 returns the same page as :80 or :443,
> the "Testing 123" default Apache test page.
>
> Any ideas how to get them to serve the DocumentRoot and
> Directory entries in their VirtualHost entries ?
>
> Thanks & Best Regards,
> Jason
>
>
> On 27/12/2021, Eric Covener  wrote:
>>> 
>>>  Directory "/opt/A"
>>
>> Did you mean DocumentRoot?
>>
>> Can you show the verbatim config for one of the virtual hosts?
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
>> For additional commands, e-mail: users-h...@httpd.apache.org
>>
>>
>

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

Re: [users@httpd] port based VirtualHosts ?

[Jason Vas Dias]

Thanks Eric -

  Yes, it was DocumentRoot, a typo in my email only - sorry .

  I now have ALL site in separate VHosts .

  I put all the default directory entries in conf/httpd.conf into
  a separate conf.d/Apache.conf :

   
 ServerName $HOST_DNS_NAME:80
 include conf.d/Apache.dir
   

  And my ssl.conf now does:

  
 ... # original ssl.conf
 ServerName $HOST_DNS_NAME:443
 include conf.d/Apache.dir
   

  And my A & B conf are both (where $PORT is either 2x080 or 1x080)
  (numbers redacted):

conf.d/A.conf:
Listen $HOST_DNS_IP:1x080 https


  ServerAdmin ${ME}@localhost
  ServerName  $HOST_DNS_NAME:1x080
  DocumentRoot "/opt/A"
  SSLEngine on
  SSLCertificateFile/etc/pki/tls/certs/localhost.crt
  SSLCertificateKeyFile /etc/pki/tls/private/localhost.key
  ErrorLog"logs/A-error_log"
  TransferLog "logs/A-access_log"
  
Options +ExecCGI +Includes +Indexes +FollowSymLinks
require all granted
  


conf.d/B.conf:

Listen $HOST_DNS_IP:2x080 https


  ServerName  $HOST_DNS_NAME:2x080
  ServerAdmin ${ME}@localhost
  DocumentRoot "/opt/B"
  SSLEngine on
  SSLCertificateFile  /etc/pki/tls/certs/localhost.crt
  SSLCertificateKeyFile /etc/pki/tls/private/localhost.key
  ErrorLog "logs/B-error_log"
  TransferLog "logs/B-access_log"
  
Options +ExecCGI +Includes +Indexes +FollowSymLinks
require all granted
  


I also created a _default_.conf file containing:




httpd starts and httpd -S says :

httpd -S
VirtualHost configuration:
*:80 $HOST_DNS_NAME  (/etc/httpd/conf.d/Apache.conf:1)
*:48080$HOST_DNS_NAME (/etc/httpd/conf.d/B.conf:5)
*:*  $HOST_DNS_NAME (/etc/httpd/conf.d/_default_.conf:1)
*:60080$HOST_DNS_NAME (/etc/httpd/conf.d/B.conf:5)
*:443   $HOST_DNS_NAME (/etc/httpd/conf.d/ssl.conf:56)

But still, a request to either $HOST_DNS_NAME:1x080 or
$HOST_DNS_NAME:2x080 returns the same page as :80 or :443,
the "Testing 123" default Apache test page.

Any ideas how to get them to serve the DocumentRoot and
Directory entries in their VirtualHost entries ?

Thanks & Best Regards,
Jason


On 27/12/2021, Eric Covener  wrote:
>> 
>>  Directory "/opt/A"
>
> Did you mean DocumentRoot?
>
> Can you show the verbatim config for one of the virtual hosts?
>
> -
> To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
> For additional commands, e-mail: users-h...@httpd.apache.org
>
>

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

Re: [users@httpd] port based VirtualHosts ?

[Eric Covener]

> 
>  Directory "/opt/A"

Did you mean DocumentRoot?

Can you show the verbatim config for one of the virtual hosts?

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

Re: [users@httpd] port based VirtualHosts ?

[Jason Vas Dias]

Many thanks Eric -

  Yes, I thought it must be supported ( and finally found :

https://www.oreilly.com/library/view/apache-the-definitive/0596002033/ch04s02s04.html
- "Port Based Virtual Hosts" -
  ) - but it is still not working.

  All Port servers still serve the default Apache websites -
  I guess I need to put these website into separate VirtualHosts
  for the *:80 and *:443 ports only ?

  Here is the output of httpd -S , with all IP & name details redacted
  (replaced by $* variable names which should be self explanatory):

# httpd -S
VirtualHost configuration:
*:2x080$HOST_DNS_NAME (/etc/httpd/conf.d/A.conf:5)
*:1x080$HOST_DNS_NAME (/etc/httpd/conf.d/B.conf:5)
*:443   $HOST_DNS_NAME (/etc/httpd/conf.d/ssl.conf:56)
ServerRoot: "/etc/httpd"
Main DocumentRoot: "/var/www/html"
Main ErrorLog: "/etc/httpd/logs/error_log"
Mutex proxy-balancer-shm: using_defaults
Mutex rewrite-map: using_defaults
Mutex authdigest-client: using_defaults
Mutex ssl-stapling: using_defaults
Mutex proxy: using_defaults
Mutex authn-socache: using_defaults
Mutex ssl-cache: using_defaults
Mutex default: dir="/run/httpd/" mechanism=default
Mutex mpm-accept: using_defaults
Mutex authdigest-opaque: using_defaults
PidFile: "/run/httpd/httpd.pid"
Define: _RH_HAS_HTTPPROTOCOLOPTIONS
Define: DUMP_VHOSTS
Define: DUMP_RUN_CFG
Define: MODPERL2
User: name="apache" id=48
Group: name="apache" id=48

I'll try putting the default *:80 Apache sites in separate vhosts also.

Thanks & Best Regards,
Jason

On 27/12/2021, Eric Covener  wrote:
>>   I guess port based VirtualHosts are not supported ?
>
> It should work just fine and is how basic SSL configurations work.  I
> suggest looking at e.g. apachectl -S output and make sure these files
> are being loaded and aren't already listed in an earlier VirtualHost.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
> For additional commands, e-mail: users-h...@httpd.apache.org
>
>

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

Re: [users@httpd] port based VirtualHosts ?

[Eric Covener]

>   I guess port based VirtualHosts are not supported ?

It should work just fine and is how basic SSL configurations work.  I
suggest looking at e.g. apachectl -S output and make sure these files
are being loaded and aren't already listed in an earlier VirtualHost.

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

Re: [users@httpd] port 80 curl connection refused.

[patrice molinchaeux]

 

Thanks

had to reset the router for some reason.

everything rocks !

 


Sent: Wednesday, May 05, 2021 at 9:34 AM
From: "Dino Ciuffetti" 
To: users@httpd.apache.org
Subject: Re: [users@httpd] port 80 curl connection refused.







curl http://123.456.7.543 (example ip address)
curl: (7) Failed to connect to 123.456.7.543 port 80: Connection refused

 







"Connection refused" means that your apache service is not bound to port TCP/80, it's down, or your routing send HTTP traffic to another host where apache is not installed.

Check if apache httpd is up and running, check if it's working on port 80 and also check your routing.





-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

Re: [users@httpd] port 80 curl connection refused.

[Dino Ciuffetti]

curl http://123.456.7.543 (http://123.456.7.543) (example ip address)
curl: (7) Failed to connect to 123.456.7.543 port 80: Connection refused
"Connection refused" means that your apache service is not bound to port 
TCP/80, it's down, or your routing send HTTP traffic to another host where 
apache is not installed.

Check if apache httpd is up and running, check if it's working on port 80 and 
also check your routing.

Re: [users@httpd] Port 80 error still there even though listening on different port

[Luca Toscano]

Hi Mike,
Il giorno lun 18 feb 2019 alle ore 04:08 Mike Starr
 ha scritto:
>
> Hi, I am still getting the ubiquitous Port 80 blocked error when starting 
> Apache even though I am listening on port 8080 in httpd.conf.
>
> What am I doing wrong?

I assume your OS is Linux, so what I'd do is run a command like "sudo
netstat -nltp" to see what process owns port 80. If it is httpd, I'd
check if the httpd.conf contain a "Listen 80" statement (if your
distribution splits config files in multiple places you might have a
"default" config somewhere that you are not aware for example).

Hope that helps!

Luca

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

Re: [users@httpd] Port Forwarding Help?

[Ruben Safir]

On 1/21/19 3:07 PM, Osman Zakir wrote:
> I can see the app on localhost on either port 8000 or port 8081.  What am I 
> doing wrong?
> 


fix your network then.


-- 
So many immigrant groups have swept through our town
that Brooklyn, like Atlantis, reaches mythological
proportions in the mind of the world - RI Safir 1998
http://www.mrbrklyn.com

DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002
http://www.nylxs.com - Leadership Development in Free Software
http://www2.mrbrklyn.com/resources - Unpublished Archive
http://www.coinhangout.com - coins!
http://www.brooklyn-living.com

Being so tracked is for FARM ANIMALS and extermination camps,
but incompatible with living as a free human being. -RI Safir 2013

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

Re: [users@httpd] Port Forwarding Help?

[Osman Zakir]

I can see the app on localhost on either port 8000 or port 8081.  What am I 
doing wrong?

Re: [users@httpd] Port Forwarding Help?

[Ruben Safir]

On Mon, Jan 21, 2019 at 04:19:00PM +, Osman Zakir wrote:
> Wait, so it's fine if I use my internal IP address?  The app will be 
> available on my public IP address in that case too?


you app is being called by apache so it doesn't matter were it is  as
long as apache can reach it.

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

Re: [users@httpd] Port Forwarding Help?

[Ruben Safir]

On Mon, Jan 21, 2019 at 04:27:38PM +, Osman Zakir wrote:
> This is what I have in the conf file at the bottom:
> "
>  "E:/programming/visual_studio_2017/Projects/currency_converter/x64/Release">
> Options All???
> Options Indexes FollowSymLinks???
> AllowOverride None???
> Require all granted???
> ???
> ???
> ???

YOUR BOX is listening on port 8000

> ServerAdmin osmanzaki...@hotmail.com???
> ServerName dragonosman.dynu.net???
> ServerAlias www.dragonosman.dynu.net???
> ErrorLog "logs/dragonosman.dynu.net-error.log"???
> CustomLog "logs/dragonosman.dynu.net-access.log" common???
> ProxyPass "/" "http://192.168.10.12:5501/;???
> ProxyPass "/?q=accesskey" "http://192.168.10.12:5501/?q=accesskey;???
> ???
> "
> 
> And I added a forwarding rule for port 8000 for the router.  But I still 
> can't see the app at my public IP address on port 8000.

Your box doesn't LIVE on your router.  Is your box where the webserver lives 
assigned the
public IP address?

what is ifconfig on the webserver box?

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

Re: [users@httpd] Port Forwarding Help?

[Osman Zakir]

This is what I have in the conf file at the bottom:
"

Options All​
Options Indexes FollowSymLinks​
AllowOverride None​
Require all granted​
​
​
​
ServerAdmin osmanzaki...@hotmail.com​
ServerName dragonosman.dynu.net​
ServerAlias www.dragonosman.dynu.net​
ErrorLog "logs/dragonosman.dynu.net-error.log"​
CustomLog "logs/dragonosman.dynu.net-access.log" common​
ProxyPass "/" "http://192.168.10.12:5501/"​
ProxyPass "/?q=accesskey" "http://192.168.10.12:5501/?q=accesskey"​
​
"

And I added a forwarding rule for port 8000 for the router.  But I still can't 
see the app at my public IP address on port 8000.

Re: [users@httpd] Port Forwarding Help?

[Eric Covener]

On Mon, Jan 21, 2019 at 11:19 AM Osman Zakir  wrote:
>
> Wait, so it's fine if I use my internal IP address?  The app will be 
> available on my public IP address in that case too?

In ProxyPass, assuming your reverse proxy and backend are on the same
internal network, yes.
As long as the reverse proxy is port forwarded, and it proxies to your
backend, the app will be available on your public IP address.




-- 
Eric Covener
cove...@gmail.com

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

Re: [users@httpd] Port Forwarding Help?

[Osman Zakir]

Wait, so it's fine if I use my internal IP address?  The app will be available 
on my public IP address in that case too?

Re: [users@httpd] Port Forwarding Help?

[Eric Covener]

On Mon, Jan 21, 2019 at 11:12 AM Osman Zakir  wrote:
>
> My server is listening on http://dragonosman.dynu.net:5501/.  Should I put 
> that there then?  Also, should the ProxyPass directive go inside the 
> VirtualHost tags or outside?

Yes. But normally you would use an internal LAN address not a dyndns
kind of thing for the link between a reverse proxy and the backend.

Probably best to move it inside. At the moment, you only have 1
virtual host, so it doesn't make a difference.


-- 
Eric Covener
cove...@gmail.com

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

Re: [users@httpd] Port Forwarding Help?

[Osman Zakir]

My server is listening on 
http://dragonosman.dynu.net:5501/.  Should I 
put that there then?  Also, should the ProxyPass directive go inside the 
VirtualHost tags or outside?

Re: [users@httpd] Port Forwarding Help?

[Eric Covener]

On Mon, Jan 21, 2019 at 10:56 AM Osman Zakir  wrote:
>
> The httpd.conf file is attached to this email.  The VirtualHost and ProxyPass 
> stuff is at the bottom.  Please let me know what I messed up now, if anything 
> at all.  And if there's something wrong, help me out with that.
>
> The first parameter to the ProxyPass directive for "/" is currently the 
> directory on my computer where the doc-root of the app is.  It's also where 
> the server executable is.  If that's right, should I also put that directory 
> for accesskey route (i.e. /?q=accesskey)?

No, the first parameter is the incoming URL prefix root you want to
forward to what's supposed to be the address of another HTTP server
(origin or backend server) in the 2nd parameter.

Your first parameter is a local filesystem path and it won't match any
request for / or /myapp.  No example looks like this.

It also looks like your 2nd parameter is the URL for the reverse proxy
itself, which would loop if the first parameter ever did match. For
the tenth time, if you don't have your application listening for HTTP
requests in some other server, you should not be setting up a reverse
proxy.

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

Re: [users@httpd] Port Forwarding Help?

[Osman Zakir]

The httpd.conf file is attached to this email.  The VirtualHost and ProxyPass 
stuff is at the bottom.  Please let me know what I messed up now, if anything 
at all.  And if there's something wrong, help me out with that.

The first parameter to the ProxyPass directive for "/" is currently the 
directory on my computer where the doc-root of the app is.  It's also where the 
server executable is.  If that's right, should I also put that directory for 
accesskey route (i.e. /?q=accesskey)?

When I try to get to "localhost:8081" in my browser now, I get an "Index of /" 
page and nothing more (8081 is the port Apache is listening on).  Trying to do 
"localhost:8000" gives an error (8000 is the reverse proxy port).


httpd.conf
Description: httpd.conf

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

Re: [users@httpd] Port Forwarding Help?

[Eric Covener]

On Mon, Jan 21, 2019 at 10:25 AM Osman Zakir  wrote:
>
> I need to know if I've set up the reverse proxy configuration correctly in 
> the conf file, and also how to fix it I did something wrong.

This has nothing to do with port forwarding in your router.  "If"
you've set it up correctly, accessing the reverse proxy directly
should result in a HTTP request sent to whatever "other" HTTP server
you have that dictates using a reverse proxy at all.

> And I also need to know how to correctly visit the app in the browser after 
> I've set it up correctly and am forwarding the port that Apache is listening 
> (if that's the only port I need to forward).

Get it working on your LAN first.  The "correct" way to visit the app
is determined by what port your reverse proxy listens on and what path
you forward to your backend with the first parameter of ProxyPass.


-- 
Eric Covener
cove...@gmail.com

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

Re: [users@httpd] Port Forwarding Help?

[Osman Zakir]

I need to know if I've set up the reverse proxy configuration correctly in the 
conf file, and also how to fix it I did something wrong.  And I also need to 
know how to correctly visit the app in the browser after I've set it up 
correctly and am forwarding the port that Apache is listening (if that's the 
only port I need to forward).

Re: [users@httpd] Port Forwarding Help?

[Eric Covener]

On Mon, Jan 21, 2019 at 10:13 AM Osman Zakir  wrote:
>
> I don't know if it's the same as what you're talking about, but I can choose 
> a range for an internal port and for external port (there are External Port 
> Start and External Port End, and Internal Port Start and Internal Port End), 
> and I can use 80 or 443 for the internal port while using a different one for 
> the external port.  Is that what you mean?

Two ranges sounds like you can map it to an alternate listening (internal) port.

-- 
Eric Covener
cove...@gmail.com

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

Re: [users@httpd] Port Forwarding Help?

[Eric Covener]

> Because if so, I'll need to choose a different port because I'm having it 
> listen on port 8080 which is being blocked by the ISP.

Unless your router allows you to forward port A to port B in the UI,
you'll have to listen on a port your ISP isn't filtering.

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

Re: [users@httpd] Port Forwarding Help?

[Osman Zakir]

I can't use port 80 or 433 for my external port because the router's using 
those ports.  8080 and 8443 are also being blocked by ISP.  So I had to use 
5501 and forward that.  I'll take away the forwarding rule for port 5501 if I 
can get the reverse proxy to work, though.

That being said, just now I tried to visit dragonosman.dynu.net:8000 after 
setting up port forwarding for port 8000, since I'm using that port for the 
VirtualHost setting in the httpd.conf file.  The file is attached to this 
message.

Do I also need to set up port forwarding for the port that Apache is listening 
on?  Because right now I can't get to my app in the browser through port 8000.  
On Chrome, I get this error: ERR_CONNECTION_REFUSED.  I asked on a Discord 
group I go to as well and one of the members there just told me that I only 
need to forward the port that Apache is listening on.  Is this correct?  
Because if so, I'll need to choose a different port because I'm having it 
listen on port 8080 which is being blocked by the ISP.


httpd.conf
Description: httpd.conf

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

Re: [users@httpd] Port Forwarding Help?

[Yehuda Katz]

If your ISP blocks port 80 and port 443, there is no way for you to host
the site without a port number.
If you can run a server on those ports, HTTPD would listen there and
reverse proxy to the internal port the app is running on (5501?). You would
not want to forward 5501 through the router because it would allow people
to bypass your reverse proxy.
You prove ownership of the URL by placing a particularly named file in
/.well-known/ and the SSL tool will check for it there. This will not work
if you aren't on a standard port (80/443).

- Y

Sent from a device with a very small keyboard and hyperactive autocorrect.

On Sun, Jan 20, 2019, 3:50 PM Osman Zakir  I found out that the problem was that I was using port 8080 which was
> blocked by my ISP.  I managed to get it to work using a different port
> (port 8443 didn't work either).
>
> Now I need to ask this: if I want to put my app behind Apache's reverse
> proxy, do I need to set up port forwarding for just the port that I set for
> the reverse proxy in ProxyPass directive, or do I also have to do it for
> the one Apache is listening on?
>
> Also, I got a free DynDNS from dynu.com and I'm serving my app on port
> 5501 on it, but is there no way I can use a URL where specifying the port
> number isn't a requirement?  The URL is http://dragonosman.dynu.net:5501/
> .  And if I want to get an SSL certificate for it, seeing as I'm hosting it
> on my own computer with a Dynamic DNS, how do I prove ownership of the
> domain when I try to use something like this? https://www.sslforfree.com/
> .
> SSL For Free - Free SSL Certificates in Minutes
> 
> Free SSL Certificate issued in less than a minute. 100% Free Forever.
> Never pay for SSL again. Thanks to Letsencrypt the first non-profit CA..
> Widely Trusted. Our free SSL certificates are trusted in 99.9% of all major
> browsers.
> www.sslforfree.com
>
>

Re: [users@httpd] Port Forwarding Help?

[Osman Zakir]

I found out that the problem was that I was using port 8080 which was blocked 
by my ISP.  I managed to get it to work using a different port (port 8443 
didn't work either).

Now I need to ask this: if I want to put my app behind Apache's reverse proxy, 
do I need to set up port forwarding for just the port that I set for the 
reverse proxy in ProxyPass directive, or do I also have to do it for the one 
Apache is listening on?

Also, I got a free DynDNS from dynu.com and I'm serving my app on port 5501 on 
it, but is there no way I can use a URL where specifying the port number isn't 
a requirement?  The URL is http://dragonosman.dynu.net:5501/ .  And if I want 
to get an SSL certificate for it, seeing as I'm hosting it on my own computer 
with a Dynamic DNS, how do I prove ownership of the domain when I try to use 
something like this? https://www.sslforfree.com/ .
SSL For Free - Free SSL Certificates in Minutes
Free SSL Certificate issued in less than a minute. 100% Free Forever. Never pay 
for SSL again. Thanks to Letsencrypt the first non-profit CA.. Widely Trusted. 
Our free SSL certificates are trusted in 99.9% of all major browsers.
www.sslforfree.com

Re: [users@httpd] port forwarding and other options for having access to my apache server through the ip address

[angel Hall-Coulston]

Hi, 
Also be very careful that you are not breaching the Terms of your ISP. They for 
obvious reasons don’t allow just anybody to serve websites or other files…. You 
have to have permission as they WILL find you out and if it’s against terms, 
they could block you… 
It’s ALWAYS best to have a static IP assigned for stability…
Don’t want to be a spoilsport, just giving fair warning !

> On 11 Jan 2019, at 22:19, John  wrote:
> 
> I'm not sure about your configuration so this might be irrelevant, but try 
> looking at all the moving parts here.
> 
> For example, since your IP is dynamic, how are you doing address resolution 
> on the Internet? Does your 
> address resolver have the correct real address? Try pinging yourself.
> 
> If that works, then see where the router is sending port 80. The internal 
> router is probably a NAT arrangement,
> so check that the port 80 destination setting is for your server machine. 
> (ie, suppose you are at Inet address 
> 205.100.1.1, and that you can really ping this address. Where does the router 
> send port 80 to?) It should
> be something like 192.168.1.xxx. Is this your local server's address? If DHCP 
> it could easily change periodically.
> If so. make the internal address static.
> 
> If your actual firewall doesn't support static NAT addresses, you can usually 
> force the issue by giving the server 
> a static address that it will always use to connect.
> 
> If all that works, then look at the firewall router's log. Most of them 
> retain a log of connections and failed
> connections. See if your attempt to connect actually made it to your firewall 
> and how it disposed of it, One
> comment, these logs are about as arcane as anything I have ever seen!
> 
> Be careful, when you change settings you can make a real mess if you guess 
> wrong! Be sure you know what
> you did so you can back out without having to re-initialize.
> 
> Just as a last desperate idea, when you make a firewall/router change, power 
> cycle it, just in case the change
> didn't get picked up.
> 
> After that, sorry, off of ideas.
> 
> John
> =
> On Fri, 2019-01-11 at 14:23 -0700, Jonathon Koyle wrote:
>> The only other suggestions I have are to Verify that your server is 
>> accessible from another machine, not blocked by a firewall or only listening 
>> on loopback.  It isn't likely to be an ISP issue unless they try to restrict 
>> you from serving a website...
>> 
>> On Fri, Jan 11, 2019, 13:54 Stathis G. Arapostathis 
>> mailto:e.arapostat...@gmail.com> wrote:
>>> well, i have a dynamic ip but this is not my problem. I also portforwarded 
>>> port 80 before sending current question but I still do not have access. 
>>> 
>>> There are some years passed since the last time I port-forwarded apache 
>>> server and I thought that maybe some additional modifications from 
>>> apache-server side are needed as the updates pass through time.
>>> 
>>> I guess I have to contact my ISP again, it could be an ISP issue.
>>> thank you very much for the quick responses.   
>>> 
>>> 
>>>  
>>> 
>>> Virus-free. www.avast.com 
>>> 
>>>  
>>> On Fri, Jan 11, 2019 at 10:37 PM Jonathon Koyle >> > wrote:
 You may also need to look into whether you have a static or dynamic IP 
 address.  Many Consumer ISP packages provide dynamic, so the public IP 
 address changes periodically, often a day or two in my experience.  Also 
 note this won't be the IP address of your host machine, but the IP 
 assigned to the router.
 
 On Fri, Jan 11, 2019 at 11:14 AM John >>> > wrote:
> Start here:
> 
> https://portforward.com/technicolor/td5130/ 
> 
> 
> What you need to do is open port 80 (unencrypted http), that is, Internet 
> browsers. Be sure 
> you have appropriate security because you are putting your machine in a 
> hostile environment!
> If you don't believe that, look at your log after a few days on the 'net!
> 
> If you plan to encrypt your pages, you will also need port 443 open 
> (HTTPS).
> 
> Good luck.
> 
> John
> 
> 
> On Fri, 2019-01-11 at 20:04 +0200, Stathis G. Arapostathis wrote:
>> Dear Sirs / Madams,
>> 
>>   I was wondering on how I could configure my router and make any other 
>> necessary configurations in order to open up my localhost to the web and 
>> letting internet users to access my locally stored pages by putting my 
>> ip address.
>> 
>> I have an old router and no support is available. My isp does not have 
>> support and I received zero responses from the 

Re: [users@httpd] port forwarding and other options for having access to my apache server through the ip address

[John]

I'm not sure about your configuration so this might be irrelevant, but try
looking at all the moving parts here.
For example, since your IP is dynamic, how are you doing address resolution on
the Internet?  Does your address resolver have the correct real address?  Try
pinging yourself.
If that works, then see where the router is sending port 80.  The internal
router is probably a NAT arrangement, so check that the port 80 destination
setting is for your server machine.  (ie, suppose you are at Inet
address 205.100.1.1, and that you can really ping this address.  Where does the
router send port 80 to?)  It should be something like 192.168.1.xxx.  Is this
your local server's address?  If DHCP it could easily change periodically.If so.
make the internal address static.
If your actual firewall doesn't support static NAT addresses, you can usually
force the issue by giving the server a static address that it will always use to
connect.  
If all that works, then look at the firewall router's log.  Most of them retain
a log of connections and failed connections.  See if your attempt to connect
actually made it to your firewall and how it disposed of it,  One comment, these
logs are about as arcane as anything I have ever seen!
Be careful, when you change settings you can make a real mess if you guess
wrong!  Be sure you know what you did so you can back out without having to re-
initialize.
Just as a last desperate idea, when you make a firewall/router change, power
cycle it, just in case the change didn't get picked up.  
After that, sorry, off of ideas.
John=On Fri, 2019-01-11 at 14:23 -0700, Jonathon
Koyle wrote:
> The only other suggestions I have are to Verify that your server is accessible
> from another machine, not blocked by a firewall or only listening on
> loopback.  It isn't likely to be an ISP issue unless they try to restrict you
> from serving a website...
> 
> On Fri, Jan 11, 2019, 13:54 Stathis G. Arapostathis  wrote:
> > well, i have a dynamic ip but this is not my problem. I also portforwarded
> > port 80 before sending current question but I still do not have access. 
> > There are some years passed since the last time I port-forwarded apache
> > server and I thought that maybe some additional modifications from apache-
> > server side are needed as the updates pass through time.
> > 
> > I guess I have to contact my ISP again, it could be an ISP issue.
> > thank you very much for the quick responses.   
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > Virus-free. www.avast.com
> > 
> > 
> > 
> > 
> > On Fri, Jan 11, 2019 at 10:37 PM Jonathon Koyle 
> > wrote:
> > > You may also need to look into whether you have a static or dynamic IP
> > > address.  Many Consumer ISP packages provide dynamic, so the public IP
> > > address changes periodically, often a day or two in my experience.  Also
> > > note this won't be the IP address of your host machine, but the IP
> > > assigned to the router.
> > > 
> > > On Fri, Jan 11, 2019 at 11:14 AM John  wrote:
> > > > Start here:
> > > >   https://portforward.com/technicolor/td5130/
> > > > What you need to do is open port 80 (unencrypted http), that is,
> > > > Internet browsers.  Be sure you have appropriate security because you
> > > > are putting your machine in a hostile environment!If you don't believe
> > > > that, look at your log after a few days on the 'net!
> > > > If you plan to encrypt your pages, you will also need port 443 open
> > > > (HTTPS).
> > > > Good luck.
> > > > John
> > > > On Fri, 2019-01-11 at 20:04 +0200, Stathis G. Arapostathis wrote:
> > > > > Dear Sirs / Madams,
> > > > >   I was wondering on how I could configure my router and make any
> > > > > other necessary configurations in order to open up my localhost to the
> > > > > web and letting internet users to access my locally stored pages by
> > > > > putting my ip address.
> > > > > 
> > > > > I have an old router and no support is available. My isp does not have
> > > > > support and I received zero responses from the router's support
> > > > > service. I think I have added a port in my router's menu but still
> > > > > internet users do not have access on it.
> > > > > 
> > > > > 
> > > > > I am using the latest ms4w package which uses apache 2.4.27 along with
> > > > > mapserver and few other mapping tools.
> > > > > 
> > > > > My router is the technicolor td5130.  
> > > > > 
> > > > > Could anyone provide some feedback please?
> > > > > 
> > > > > Thank you. 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > >   
> > > > > 
> > > > >   Virus-free. www.avast.com
> > > > >   
> > > > >   
> > > > > 

Re: [users@httpd] port forwarding and other options for having access to my apache server through the ip address

[Jonathon Koyle]

The only other suggestions I have are to Verify that your server is
accessible from another machine, not blocked by a firewall or only
listening on loopback.  It isn't likely to be an ISP issue unless they try
to restrict you from serving a website...

On Fri, Jan 11, 2019, 13:54 Stathis G. Arapostathis <
e.arapostat...@gmail.com wrote:

> well, i have a dynamic ip but this is not my problem. I also portforwarded
> port 80 before sending current question but I still do not have access.
>
> There are some years passed since the last time I port-forwarded apache
> server and I thought that maybe some additional modifications from
> apache-server side are needed as the updates pass through time.
>
> I guess I have to contact my ISP again, it could be an ISP issue.
> thank you very much for the quick responses.
>
>
>
> 
>  Virus-free.
> www.avast.com
> 
> <#m_-8740454897196676016_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
> On Fri, Jan 11, 2019 at 10:37 PM Jonathon Koyle 
> wrote:
>
>> You may also need to look into whether you have a static or dynamic IP
>> address.  Many Consumer ISP packages provide dynamic, so the public IP
>> address changes periodically, often a day or two in my experience.  Also
>> note this won't be the IP address of your host machine, but the IP assigned
>> to the router.
>>
>> On Fri, Jan 11, 2019 at 11:14 AM John  wrote:
>>
>>> Start here:
>>>
>>> https://portforward.com/technicolor/td5130/
>>>
>>> What you need to do is open port 80 (unencrypted http), that is,
>>> Internet browsers. Be sure
>>> you have appropriate security because you are putting your machine in a
>>> hostile environment!
>>> If you don't believe that, look at your log after a few days on the 'net!
>>>
>>> If you plan to encrypt your pages, you will also need port 443 open
>>> (HTTPS).
>>>
>>> Good luck.
>>>
>>> John
>>> 
>>>
>>> On Fri, 2019-01-11 at 20:04 +0200, Stathis G. Arapostathis wrote:
>>>
>>> Dear Sirs / Madams,
>>>
>>>   I was wondering on how I could configure my router and make any other
>>> necessary configurations in order to open up my localhost to the web and
>>> letting internet users to access my locally stored pages by putting my ip
>>> address.
>>>
>>> I have an old router and no support is available. My isp does not have
>>> support and I received zero responses from the router's support service. I
>>> think I have added a port in my router's menu but still internet users do
>>> not have access on it.
>>>
>>>
>>> I am using the latest ms4w package which uses apache 2.4.27 along with
>>> mapserver and few other mapping tools.
>>>
>>> My router is the technicolor td5130.
>>>
>>> Could anyone provide some feedback please?
>>>
>>> Thank you.
>>>
>>>
>>>
>>> 
>>>  Virus-free.
>>> www.avast.com
>>> 
>>> <#m_-8740454897196676016_m_-632829969495664661_m_8256112442323143262_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>>
>>>
>>
>> --
>> Jonathon Koyle
>>
>

Re: [users@httpd] port forwarding and other options for having access to my apache server through the ip address

[Stathis G. Arapostathis]

well, i have a dynamic ip but this is not my problem. I also portforwarded
port 80 before sending current question but I still do not have access.

There are some years passed since the last time I port-forwarded apache
server and I thought that maybe some additional modifications from
apache-server side are needed as the updates pass through time.

I guess I have to contact my ISP again, it could be an ISP issue.
thank you very much for the quick responses.



Virus-free.
www.avast.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Fri, Jan 11, 2019 at 10:37 PM Jonathon Koyle 
wrote:

> You may also need to look into whether you have a static or dynamic IP
> address.  Many Consumer ISP packages provide dynamic, so the public IP
> address changes periodically, often a day or two in my experience.  Also
> note this won't be the IP address of your host machine, but the IP assigned
> to the router.
>
> On Fri, Jan 11, 2019 at 11:14 AM John  wrote:
>
>> Start here:
>>
>> https://portforward.com/technicolor/td5130/
>>
>> What you need to do is open port 80 (unencrypted http), that is, Internet
>> browsers. Be sure
>> you have appropriate security because you are putting your machine in a
>> hostile environment!
>> If you don't believe that, look at your log after a few days on the 'net!
>>
>> If you plan to encrypt your pages, you will also need port 443 open
>> (HTTPS).
>>
>> Good luck.
>>
>> John
>> 
>>
>> On Fri, 2019-01-11 at 20:04 +0200, Stathis G. Arapostathis wrote:
>>
>> Dear Sirs / Madams,
>>
>>   I was wondering on how I could configure my router and make any other
>> necessary configurations in order to open up my localhost to the web and
>> letting internet users to access my locally stored pages by putting my ip
>> address.
>>
>> I have an old router and no support is available. My isp does not have
>> support and I received zero responses from the router's support service. I
>> think I have added a port in my router's menu but still internet users do
>> not have access on it.
>>
>>
>> I am using the latest ms4w package which uses apache 2.4.27 along with
>> mapserver and few other mapping tools.
>>
>> My router is the technicolor td5130.
>>
>> Could anyone provide some feedback please?
>>
>> Thank you.
>>
>>
>>
>> 
>>  Virus-free.
>> www.avast.com
>> 
>> <#m_-632829969495664661_m_8256112442323143262_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>
>>
>
> --
> Jonathon Koyle
>

Re: [users@httpd] port forwarding and other options for having access to my apache server through the ip address

[Jonathon Koyle]

You may also need to look into whether you have a static or dynamic IP
address.  Many Consumer ISP packages provide dynamic, so the public IP
address changes periodically, often a day or two in my experience.  Also
note this won't be the IP address of your host machine, but the IP assigned
to the router.

On Fri, Jan 11, 2019 at 11:14 AM John  wrote:

> Start here:
>
> https://portforward.com/technicolor/td5130/
>
> What you need to do is open port 80 (unencrypted http), that is, Internet
> browsers. Be sure
> you have appropriate security because you are putting your machine in a
> hostile environment!
> If you don't believe that, look at your log after a few days on the 'net!
>
> If you plan to encrypt your pages, you will also need port 443 open
> (HTTPS).
>
> Good luck.
>
> John
> 
>
> On Fri, 2019-01-11 at 20:04 +0200, Stathis G. Arapostathis wrote:
>
> Dear Sirs / Madams,
>
>   I was wondering on how I could configure my router and make any other
> necessary configurations in order to open up my localhost to the web and
> letting internet users to access my locally stored pages by putting my ip
> address.
>
> I have an old router and no support is available. My isp does not have
> support and I received zero responses from the router's support service. I
> think I have added a port in my router's menu but still internet users do
> not have access on it.
>
>
> I am using the latest ms4w package which uses apache 2.4.27 along with
> mapserver and few other mapping tools.
>
> My router is the technicolor td5130.
>
> Could anyone provide some feedback please?
>
> Thank you.
>
>
>
> 
>  Virus-free.
> www.avast.com
> 
> <#m_8256112442323143262_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
>

-- 
Jonathon Koyle

Re: [users@httpd] port forwarding and other options for having access to my apache server through the ip address

[John]

Start here:
  https://portforward.com/technicolor/td5130/
What you need to do is open port 80 (unencrypted http), that is, Internet
browsers.  Be sure you have appropriate security because you are putting your
machine in a hostile environment!If you don't believe that, look at your log
after a few days on the 'net!
If you plan to encrypt your pages, you will also need port 443 open (HTTPS).
Good luck.
John
On Fri, 2019-01-11 at 20:04 +0200, Stathis G. Arapostathis wrote:
> Dear Sirs / Madams,
>   I was wondering on how I could configure my router and make any other
> necessary configurations in order to open up my localhost to the web and
> letting internet users to access my locally stored pages by putting my ip
> address.
> 
> I have an old router and no support is available. My isp does not have support
> and I received zero responses from the router's support service. I think I
> have added a port in my router's menu but still internet users do not have
> access on it.
> 
> 
> I am using the latest ms4w package which uses apache 2.4.27 along with
> mapserver and few other mapping tools.
> 
> My router is the technicolor td5130.  
> 
> Could anyone provide some feedback please?
> 
> Thank you. 
> 
> 
> 
> 
>   
> 
>   Virus-free. www.avast.com
>   
>   
> 

Re: [users@httpd] port redirecting mapping

[Thomas Eckert]

I'm confused as to what your setup and intention is. From your original
message I assumed you were talking about a normal server but your
configuration example looks like a
reverse proxy. Also, I assumed you wanted requests to
http://domain_name:3030/ to be redirected but then you said *all* requests
to port 3030.

Does this suit your problem ?

Listen 10.10.10.10:3030 http
VirtualHost *:3030
  ServerName my_redirect_host
  Redirect permanent / http://domain_name/
/VirtualHost


On Mon, Feb 10, 2014 at 2:57 PM, varun varun.bhuvanend...@gmail.com wrote:

  I am trying to redirect a link with a port number to another link. I had
 tried this with the intention
 that all requests ending with :3030/ should be mapped to
 http://domain_name/

* Proxy **
 *Order allow,deny*
 *Allow from all*
 */Proxy*
 *ProxyPass :3030/ http://domain_name/ http://domain_name/*
 *ProxyPassReverse :3030/ http://domain_name/ http://domain_name/*
 This is not working, as a request like http://domain:3030 is not
 redirecting.

 But when i tries
 ProxyPass / http://domain_name:3030/
 ProxyPassReverse / http://domain_name:3030/
 A request like this *http://domain_name http://domain_name* redirects
 to *http://domain_name:3030 http://domain_name:3030*

 Also tries Redirect
 *Redirect :3030 http://domain_name http://domain_name*

 rewrite_module is enabled.

 Is there any config error or the approach is bad.


 On Monday 10 February 2014 06:21 PM, Thomas Eckert wrote:

   Assuming you have a working config for a server/vhost on
 domain_name:3030, then how about
   Redirect permanent / http://domain_name:3000/
 ? See http://httpd.apache.org/docs/current/mod/mod_alias.html#redirectand 
 friends.

  Restricted access is a bit vague but
 http://httpd.apache.org/docs/current/howto/access.html is a good start.



 On Mon, Feb 10, 2014 at 12:58 PM, varun varun.bhuvanend...@gmail.comwrote:

  Is it possible to redirect a request for one port to another one.
 Say a request like *http://domain_name:3030 http://domain_name:3030*be 
 accepted and
 redirected/mapped, so that the server should be able to process the
 request like* http://domain_name:3000 http://domain_name:3000*. And a
 direct request like *http://domain_name:3000 http://domain_name:3000*
 should be restricted.
 Is there any modules, directive in apache. I am new to apache. On Ubuntu
 12.04.



 --
 kind regards
 varun http://varun.bounceme.net/

Re: [users@httpd] port redirecting mapping

[Varun Bhuvanendran]

Thomas
This was what i am looking for. Thnaks thomas.
what i was trying to do is, allow access to *http://domain_name
http://domain_name *,
if a request like *http://domain_name:3030 http://domain_name:3030  *comes
it should be
redirected/mapped to another link. From the above help i could
redirect a request with :3030 to http://domain_name

I tried the *RewriteRule *with the intention to replace the :3030 with 80
from the url* http://domain_name:3030 http://domain_name:3030* like this
*VirtualHost *:80*


*RewriteEngine on  RewriteCond %{QUERY_STRING} ^(.*):3030(.*)$
RewriteRule ^(.*)$ $%?:80% [L,R=301]*
*/VirtualHost*
this seems not working. Is there any syntax error or something. Does this
rewrite part be inside *VirtualHost *:3030* ... */VirtualHost*



On Thu, Feb 13, 2014 at 3:16 PM, Thomas Eckert
thomas.r.w.eck...@gmail.comwrote:

 I'm confused as to what your setup and intention is. From your original
 message I assumed you were talking about a normal server but your
 configuration example looks like a
 reverse proxy. Also, I assumed you wanted requests to
 http://domain_name:3030/ to be redirected but then you said *all*
 requests to port 3030.

 Does this suit your problem ?

 Listen 10.10.10.10:3030 http
 VirtualHost *:3030
   ServerName my_redirect_host
   Redirect permanent / http://domain_name/
 /VirtualHost


 On Mon, Feb 10, 2014 at 2:57 PM, varun varun.bhuvanend...@gmail.comwrote:

  I am trying to redirect a link with a port number to another link. I had
 tried this with the intention
 that all requests ending with :3030/ should be mapped to
 http://domain_name/

* Proxy **
 *Order allow,deny*
 *Allow from all*
 */Proxy*
 *ProxyPass :3030/ http://domain_name/ http://domain_name/*
 *ProxyPassReverse :3030/ http://domain_name/ http://domain_name/*
 This is not working, as a request like http://domain:3030 is not
 redirecting.

 But when i tries
 ProxyPass / http://domain_name:3030/
 ProxyPassReverse / http://domain_name:3030/
 A request like this *http://domain_name http://domain_name* redirects
 to *http://domain_name:3030 http://domain_name:3030*

 Also tries Redirect
 *Redirect :3030 http://domain_name http://domain_name*

 rewrite_module is enabled.

 Is there any config error or the approach is bad.


 On Monday 10 February 2014 06:21 PM, Thomas Eckert wrote:

   Assuming you have a working config for a server/vhost on
 domain_name:3030, then how about
   Redirect permanent / http://domain_name:3000/
 ? See http://httpd.apache.org/docs/current/mod/mod_alias.html#redirectand 
 friends.

  Restricted access is a bit vague but
 http://httpd.apache.org/docs/current/howto/access.html is a good start.



 On Mon, Feb 10, 2014 at 12:58 PM, varun varun.bhuvanend...@gmail.comwrote:

  Is it possible to redirect a request for one port to another one.
 Say a request like *http://domain_name:3030 http://domain_name:3030*be 
 accepted and
 redirected/mapped, so that the server should be able to process the
 request like* http://domain_name:3000 http://domain_name:3000*. And a
 direct request like *http://domain_name:3000 http://domain_name:3000*
 should be restricted.
 Is there any modules, directive in apache. I am new to apache. On Ubuntu
 12.04.



 --
 kind regards
 varun http://varun.bounceme.net/





-- 
kind regards
varun http://varun.bounceme.net

Re: [users@httpd] port redirecting mapping

[Thomas Eckert]

The problem with your vhost is that it responds to requests on port 80 and
if a request hits your server on port 3030 that vhost is simply not used.
That's what *VirtualHost *:80* does. Can't help you with the Rewrite
stuff, I've kept my distance from it so far. You would need someone else to
look over that, in case you still wanted to use it.


On Thu, Feb 13, 2014 at 11:24 AM, Varun Bhuvanendran 
varun.bhuvanend...@gmail.com wrote:

 Thomas
 This was what i am looking for. Thnaks thomas.
 what i was trying to do is, allow access to *http://domain_name
 http://domain_name *,
 if a request like *http://domain_name:3030 http://domain_name:3030  *comes
 it should be
 redirected/mapped to another link. From the above help i could
 redirect a request with :3030 to http://domain_name

 I tried the *RewriteRule *with the intention to replace the :3030 with 80
 from the url* http://domain_name:3030 http://domain_name:3030* like this
 *VirtualHost *:80*


 *RewriteEngine on  RewriteCond %{QUERY_STRING} ^(.*):3030(.*)$
 RewriteRule ^(.*)$ $%?:80% [L,R=301]*
 */VirtualHost*
 this seems not working. Is there any syntax error or something. Does this
 rewrite part be inside *VirtualHost *:3030* ... */VirtualHost*



 On Thu, Feb 13, 2014 at 3:16 PM, Thomas Eckert 
 thomas.r.w.eck...@gmail.com wrote:

 I'm confused as to what your setup and intention is. From your original
 message I assumed you were talking about a normal server but your
 configuration example looks like a
 reverse proxy. Also, I assumed you wanted requests to
 http://domain_name:3030/ to be redirected but then you said *all*
 requests to port 3030.

 Does this suit your problem ?

 Listen 10.10.10.10:3030 http
 VirtualHost *:3030
   ServerName my_redirect_host
   Redirect permanent / http://domain_name/
 /VirtualHost


 On Mon, Feb 10, 2014 at 2:57 PM, varun varun.bhuvanend...@gmail.comwrote:

  I am trying to redirect a link with a port number to another link. I
 had tried this with the intention
 that all requests ending with :3030/ should be mapped to
 http://domain_name/

* Proxy **
 *Order allow,deny*
 *Allow from all*
 */Proxy*
 *ProxyPass :3030/ http://domain_name/ http://domain_name/*
 *ProxyPassReverse :3030/ http://domain_name/ http://domain_name/*
 This is not working, as a request like http://domain:3030 is not
 redirecting.

 But when i tries
 ProxyPass / http://domain_name:3030/
 ProxyPassReverse / http://domain_name:3030/
 A request like this *http://domain_name http://domain_name* redirects
 to *http://domain_name:3030 http://domain_name:3030*

 Also tries Redirect
 *Redirect :3030 http://domain_name http://domain_name*

 rewrite_module is enabled.

 Is there any config error or the approach is bad.


 On Monday 10 February 2014 06:21 PM, Thomas Eckert wrote:

   Assuming you have a working config for a server/vhost on
 domain_name:3030, then how about
   Redirect permanent / http://domain_name:3000/
 ? See http://httpd.apache.org/docs/current/mod/mod_alias.html#redirectand 
 friends.

  Restricted access is a bit vague but
 http://httpd.apache.org/docs/current/howto/access.html is a good start.



 On Mon, Feb 10, 2014 at 12:58 PM, varun varun.bhuvanend...@gmail.comwrote:

  Is it possible to redirect a request for one port to another one.
 Say a request like *http://domain_name:3030 http://domain_name:3030*be 
 accepted and
 redirected/mapped, so that the server should be able to process the
 request like* http://domain_name:3000 http://domain_name:3000*. And
 a direct request like *http://domain_name:3000
 http://domain_name:3000*
 should be restricted.
 Is there any modules, directive in apache. I am new to apache. On
 Ubuntu 12.04.



 --
 kind regards
 varun http://varun.bounceme.net/





 --
 kind regards
 varun http://varun.bounceme.net

Re: [users@httpd] port redirecting mapping

[Varun Bhuvanendran]

It was so helpful.
Thanks thomas
On Feb 13, 2014 6:44 PM, Thomas Eckert thomas.r.w.eck...@gmail.com
wrote:

 The problem with your vhost is that it responds to requests on port 80 and
 if a request hits your server on port 3030 that vhost is simply not used.
 That's what *VirtualHost *:80* does. Can't help you with the Rewrite
 stuff, I've kept my distance from it so far. You would need someone else to
 look over that, in case you still wanted to use it.


 On Thu, Feb 13, 2014 at 11:24 AM, Varun Bhuvanendran 
 varun.bhuvanend...@gmail.com wrote:

 Thomas
 This was what i am looking for. Thnaks thomas.
 what i was trying to do is, allow access to *http://domain_name
 http://domain_name *,
  if a request like *http://domain_name:3030 http://domain_name:3030  *comes
 it should be
 redirected/mapped to another link. From the above help i could
 redirect a request with :3030 to http://domain_name

 I tried the *RewriteRule *with the intention to replace the :3030 with
 80 from the url* http://domain_name:3030 http://domain_name:3030* like
 this
 *VirtualHost *:80*


 *RewriteEngine on  RewriteCond %{QUERY_STRING} ^(.*):3030(.*)$
 RewriteRule ^(.*)$ $%?:80% [L,R=301]*
 */VirtualHost*
 this seems not working. Is there any syntax error or something. Does this
 rewrite part be inside *VirtualHost *:3030* ... */VirtualHost*



 On Thu, Feb 13, 2014 at 3:16 PM, Thomas Eckert 
 thomas.r.w.eck...@gmail.com wrote:

 I'm confused as to what your setup and intention is. From your original
 message I assumed you were talking about a normal server but your
 configuration example looks like a
 reverse proxy. Also, I assumed you wanted requests to
 http://domain_name:3030/ to be redirected but then you said *all*
 requests to port 3030.

 Does this suit your problem ?

 Listen 10.10.10.10:3030 http
 VirtualHost *:3030
   ServerName my_redirect_host
   Redirect permanent / http://domain_name/
 /VirtualHost


 On Mon, Feb 10, 2014 at 2:57 PM, varun varun.bhuvanend...@gmail.comwrote:

  I am trying to redirect a link with a port number to another link. I
 had tried this with the intention
 that all requests ending with :3030/ should be mapped to
 http://domain_name/

* Proxy **
 *Order allow,deny*
 *Allow from all*
 */Proxy*
 *ProxyPass :3030/ http://domain_name/ http://domain_name/*
 *ProxyPassReverse :3030/ http://domain_name/ http://domain_name/*
 This is not working, as a request like http://domain:3030 is not
 redirecting.

 But when i tries
 ProxyPass / http://domain_name:3030/
 ProxyPassReverse / http://domain_name:3030/
 A request like this *http://domain_name http://domain_name*redirects to 
 *http://domain_name:3030
 http://domain_name:3030*

 Also tries Redirect
 *Redirect :3030 http://domain_name http://domain_name*

 rewrite_module is enabled.

 Is there any config error or the approach is bad.


 On Monday 10 February 2014 06:21 PM, Thomas Eckert wrote:

   Assuming you have a working config for a server/vhost on
 domain_name:3030, then how about
   Redirect permanent / http://domain_name:3000/
 ? See http://httpd.apache.org/docs/current/mod/mod_alias.html#redirectand 
 friends.

  Restricted access is a bit vague but
 http://httpd.apache.org/docs/current/howto/access.html is a good start.



 On Mon, Feb 10, 2014 at 12:58 PM, varun 
 varun.bhuvanend...@gmail.comwrote:

  Is it possible to redirect a request for one port to another one.
 Say a request like *http://domain_name:3030 http://domain_name:3030*be 
 accepted and
 redirected/mapped, so that the server should be able to process the
 request like* http://domain_name:3000 http://domain_name:3000*. And
 a direct request like *http://domain_name:3000
 http://domain_name:3000*
 should be restricted.
 Is there any modules, directive in apache. I am new to apache. On
 Ubuntu 12.04.



 --
 kind regards
 varun http://varun.bounceme.net/





 --
 kind regards
 varun http://varun.bounceme.net

Re: [users@httpd] port redirecting mapping

[Thomas Eckert]

Assuming you have a working config for a server/vhost on domain_name:3030,
then how about
  Redirect permanent / http://domain_name:3000/
? See http://httpd.apache.org/docs/current/mod/mod_alias.html#redirect and
friends.

Restricted access is a bit vague but
http://httpd.apache.org/docs/current/howto/access.html is a good start.



On Mon, Feb 10, 2014 at 12:58 PM, varun varun.bhuvanend...@gmail.comwrote:

  Is it possible to redirect a request for one port to another one.
 Say a request like *http://domain_name:3030 http://domain_name:3030* be
 accepted and
 redirected/mapped, so that the server should be able to process the
 request like* http://domain_name:3000 http://domain_name:3000*. And a
 direct request like *http://domain_name:3000 http://domain_name:3000*
 should be restricted.
 Is there any modules, directive in apache. I am new to apache. On Ubuntu
 12.04.

Re: [users@httpd] port redirecting mapping

[varun]

I am trying to redirect a link with a port number to another link. I had 
tried this with the intention

that all requests ending with :3030/ should be mapped to http://domain_name/

*Proxy ***
**Order allow,deny**
**Allow from all**
**/Proxy**
**ProxyPass :3030/ http://domain_name/**
**ProxyPassReverse :3030/ http://domain_name/*
This is not working, as a request like http://domain:3030 is not 
redirecting.


But when i tries
ProxyPass / http://domain_name:3030/
ProxyPassReverse / http://domain_name:3030/
A request like this *http://domain_name* redirects to 
*http://domain_name:3030*


Also tries Redirect
*Redirect :3030 http://domain_name*

rewrite_module is enabled.

Is there any config error or the approach is bad.

On Monday 10 February 2014 06:21 PM, Thomas Eckert wrote:
Assuming you have a working config for a server/vhost on 
domain_name:3030, then how about

  Redirect permanent / http://domain_name:3000/
? See http://httpd.apache.org/docs/current/mod/mod_alias.html#redirect 
and friends.


Restricted access is a bit vague but 
http://httpd.apache.org/docs/current/howto/access.html is a good start.




On Mon, Feb 10, 2014 at 12:58 PM, varun varun.bhuvanend...@gmail.com 
mailto:varun.bhuvanend...@gmail.com wrote:


Is it possible to redirect a request for one port to another one.
Say a request like *http://domain_name:3030* be accepted and
redirected/mapped, so that the server should be able to process the
request like*http://domain_name:3000*. And a direct request like
*http://domain_name:3000*
should be restricted.
Is there any modules, directive in apache. I am new to apache. On
Ubuntu 12.04.




--
kind regards
varun http://varun.bounceme.net/