Thank you all for nmap and traceroute report.
@Otis Dewitt,
> You are being firewalld, those ports are not available from outside.
>
Do you mean the firewall of my OS (Ubuntu) or is there any other levels of
firewall?
Like at my router level (even though it's there, since I've port forwarded
it w
You are being firewalld, those ports are not available from outside.
On Tue, Jan 14, 2020 at 3:23 PM Larry Irwin (work) <
larry.ir...@ccamedical.com> wrote:
> nmap shows all ports as filtered:
>
> # nmap -Pn padmahasa.ddns.net
>
> Starting Nmap 7.01 ( https://nmap.org ) at 2020-01-14 15:17 EST
>
nmap shows all ports as filtered:
# nmap -Pn padmahasa.ddns.net
Starting Nmap 7.01 ( https://nmap.org ) at 2020-01-14 15:17 EST
Nmap scan report for padmahasa.ddns.net (103.228.221.102)
Host is up.
rDNS record for 103.228.221.102: 103.228.221.102.static.belltele.in
All 1000 scanned ports on padm
The IPnumber associated with padmahasa.ddns.net (103.228.221.102) is
not reachable via ping or traceroute. A traceroute ends at:
43.254.160.42.static.belltele.in (43.254.160.42)
Additionally, attempting to telnet to either port 80 or 8080 on
103.228.221.102 results in a "network hang".
So, i
Hello @Richard and @Monah baki
@Richard,
> -- what is the public IPnumber of your server?
>
I'm not sure whether it's OK or not to tell my public IP openly. But I can
give partial IP address.
xxx.xxx.221.102
> -- what is the public DNS name for your server (i.e., the dns entry
>
padmahasa.ddns.n
Check firewall
On Tue, Jan 14, 2020 at 10:43 AM Richard
wrote:
> Looking back some months I'm not finding the beginning of this
> thread, so maybe you should start fresh.
>
> -- what is the public IPnumber of your server?
>
> -- what is the public DNS name for your server (i.e., the dns entry
>
Looking back some months I'm not finding the beginning of this
thread, so maybe you should start fresh.
-- what is the public IPnumber of your server?
-- what is the public DNS name for your server (i.e., the dns entry
that points to the public IPnumber)?
> Date: Tuesday, January 14, 2020 0
Hi,
On my client browser I see that POST requests are properly sent when
using this reverse proxy configuration:
TraceEnable off
ProxyRequests Off
ProxyPass / http://backend:8080/
ProxyPassReverse / http://backend:8080/
ProxyPreserveHost On
Request URL: ht
> RewriteRule ^/2/(.*)$ https://my_reverse_proxy/rp/1/2/$1
>
> So:
> 1) why do I need to specify an absolute URL?
> 2) is there a variable name I could use instead of my_reverse_proxy?
To answer 2) myself: %{SERVER_NAME}.
I still haven't figured out 1) though.
On Tue, Jan 14, 2020 at 12:05 PM Vieri Di Paola wrote:
> The client browser tries to connect to
>
> https://my_apache_reverse_proxy/2/css/bootstrap.12pt.css
>
> instead of
>
> https://my_apache_reverse_proxy/rp/1/2/css/bootstrap.12pt.css (typo corrected)
> or
> https://my_apache_reverse_proxy/pr/
On Tue, Jan 14, 2020 at 11:48 AM Colin 't Hart wrote:
>
> Looks like you have a transposition typo in your rewrite rule.
Thanks for seeing that typo. I fixed it, but in any case that wasn't
it because there is no match on that rewrite rule.
The client browser tries to connect to
https://my_apac
Looks like you have a transposition typo in your rewrite rule.
/Colin
On Tue, 14 Jan 2020 at 11:42, Vieri Di Paola wrote:
> Hi,
>
> I can successfully access a backend server through directives like these:
>
> ProxyPass / http://192.168.250.1:8080/
> ProxyPassReverse / http://19
Hi,
I can successfully access a backend server through directives like these:
ProxyPass / http://192.168.250.1:8080/
ProxyPassReverse / http://192.168.250.1:8080/
However, I'm having trouble if I use this other configuration:
ProxyPass /rp/1/ http://192.168.250.1:8080/
13 matches
Mail list logo
