Reverse proxy for Kibana is not working on Windows Server 2012.
I've followed the steps to configure reverse proxy to Kibana but there seems to be some problem as the reverse proxy Kibana is not loading any data whereas the localhost Kibana is working just fine.
Please go to question on https://security.stackexchange.com/questions/145846/elk-stack-reverse-proxy-configuration for details.
probably a cross domain issue, which is disallowed as default in elasticsearch.
add the following to elasticsearch.yml
http.cors.enabled : true
http.cors.allow-origin : "*"
http.cors.allow-methods : OPTIONS, HEAD, GET, POST, PUT, DELETE
http.cors.allow-headers : X-Requested-With,X-Auth-Token,Content-Type, Content-Length
Related
I posted this question on gis.stackexchange (gis.stackexchange.com/questions/383728/geoserver-over-https) but they closed it considering off-topic... (it seems that geoserver and WMS are not gis questions...)
Anyway, I installed GeoServer 2.18.1 on a windows 2008 server with IIS7. On layer preview I can see my layers on OpenLayers, so everything is ok. The URL of the preview is (http)mysite.com:8080/geoserver/tiger/wms?service=WMS (etc).
I need to use GeoServer over HTTPS on a PHP website, so I did:
installed HTTPS certificate on IIS
on geoserver, under global settings, added "(https)mysite.com:8080/geoserver" to Proxy Base URL
But now, when I preview the same layer I see a blank map. Using inspector I found an error on the request URL: SSL_ERROR_RX_RECORD_TOO_LONG
So, GeoServer WMS works ok over HTTP but not over HTTPS.
I found some related posts but they use other configuration like tomcat/apache/other, mine uses windows server/IIS/JRE/geoserver.
Any idea? Did I miss any configuration?
I am not an expert, from my recent experience deploying a GeoServer.
Geoserver runs on port:8080 (not secure) so the request has to be proxied on this port
You have to set up a reverse proxy server using IIS
I can not help you further, I have done recently this by using apache.
I am trying to setup SonarQube with SSL on Windows Server 2019. I can access the SonarQube server locally on the server using http://localhost:9000.
I followed the exact steps as outlined here to setup reverse proxy in IIS using URL Rewrite module. I see the Re-Write URL set to http://http://localhost:9000/{R:1}
However when I browse https://sonarqube.mydomain.com I get the error below
502 - Web server received an invalid response while acting as a gateway or proxy server.
Is there anything i need to enable in SonarQube to enable Reverse Proxy?
I could not find anything in website's logs %SystemDrive%\inetpub\logs\LogFiles
found it
I don't know why URL Rewrite module was adding URL as http://http://localhost:9000/{R:1}
I manually changed it to http://localhost:9000/{R:1} and it worked
I use an IIS as reverse proxy. However, the target page can only be reached via a "regular" proxy.
Currently I always get a bad gateway error. My guess is that the rewrite module of the IIS does not consider the proxy settings of the system and therefore does not get a connection to the target page.
Do I have to define own proxy settings for the rewrite module? Or is it even possible to use a reverse proxy behind a normal proxy with the IIS?
According to your description, I suggest you could try to add the proxy setting in the applicatiohost.config file.
This will make all the request to use the proxy to send to another server.
More details, you could refer to below setting:
Related article: https://learn.microsoft.com/en-us/dotnet/framework/configure-apps/file-schema/network/defaultproxy-element-network-settings
Applicationhost.config file path:
C:\Windows\System32\inetsrv\config\
Setting example:
<system.net>
<defaultProxy>
<proxy
proxyaddress="http://10.0.2.231:42"
bypassonlocal="true"
/>
</defaultProxy>
</system.net>
I could successfully get Kibana 3 hosted on IIS by adding a couple of MIME types (".json" and ".").
However, the same trick doesn't seem to be working in Kibana 4, I haven't dug deep yet as to why or what has changed, has anybody achieved this?
P.S. I don't want to do a reverse proxy as some people have suggested, this is because the server in which it resides already has a reverse proxy for something else and its rules will conflict with that of kibana 4 and I don't want to put up another server just for this.
Confluence IIS Reverse Proxy Setup
I have set up a reverse proxy on IIS 7.5 for Atlassian Confluence according to instructions found in the internet.
I wanted to redirect all traffic to "docs.unimaze.com" to "localhost:8090" on the same server.
This is how I did it:
Installed URL Rewrite 2.0
Installed Application Request Routing 3.0
Set up a reverse proxy rule:
Match URL: Matches the pattern (.*) using regular expressions (ignore case)
Conditions: (none)
Server variables: (none)
Action: Rewrite with http://localhost:8090/{R:1} (append to query string and stop processing of subsequent rules.
The only other thing I had to in order to make everything work (from https://serverfault.com/questions/76013/iis6-vs-iis7-and-iis7-5-handling-urls-with-plus-sign-in-base-not-querystr) was to run this command on the server so that URL's with "plus signs" in the URL's would be allowed.
%windir%\system32\inetsrv\appcmd set config "WebSiteName"
-section:system.webServer/security/requestFiltering -allowDoubleEscaping:true
Problem with external redirects
Confluence itself, seems to work perfectly BUT when attempting to edit a module from an external application (LucidChart Diagrams it fails), because a redirection to the external application also is rewritten, e.g. an attempt is made to redirect to this URL:
http://docs.unimaze.com/documents/edit/4b157fd9-8e28-4d70-8587-0fdd0839fbca?callback=...
when the redirect should actually be to the external application, so it should remain untouched by the rewriting rule:
https://www.lucidchart.com/documents/edit/4b157fd9-8e28-4d70-8587-0fdd0839fbca?callback=...
Is there an easy way to solve this?
This here helped: appcmd.exe set config -section:system.webServer/proxy /reverseRewriteHostInResponseHeaders:"False" -commit:apphost
In UI, the setting corresponding to this action on the Application Request Routing in IIS on the server node (select „Server Proxy Settings“) should be unchecked.
However, this had the effect that the page can not be loaded in Internet Explorer 11 L
The page is shown, but with empty space where the diagram is and it tries loading something forever.
In Firefox and Chrome it works fine.
I have no idea why it "freezes" in IE 11. Will check from other machines to see if this is always happening or not.
The easiest way to handle this is to take advantage of IIS host headers and make the proxied site believe it is responding as www.example.com:80 rather than localhost:8080. It turns out the AAR reverse proxy has an equivalent of Apache's ProxyPerserveHost setting it just isn't very well documented nor exposed in the UI.
To enable this setting you will need to open an elevated shell and run:
%windir%\system32\inetsrv\appcmd.exe set config -section:system.webServer/proxy -preserveHostHeader:true
Then configure the target site to listen at 127.0.0.1:80 with the appropriate host header and then configure the proxy to proxy back to localhost with the request and it should line up.