If you think it would help future users with this problem you could add
this information with an outline of the problem and this solution to the
running in production pages of the user manual
Ian
On Wed, 3 Aug 2022 at 16:25, Frans Fierens wrote:
> Wow! This is indeed the solution, together with the nginx config below
> (the allow/deny is to deny internet access). Thanks!!
>
> best regards
>
> Frans
>
> location /geoserver/ {
> allow x.x.x.x;
> deny all;
> proxy_pass http://yourgeoserver:8080/geoserver/;
> proxy_pass_header Set-Cookie;
> proxy_set_header Host $host;
> proxy_set_header X-Forwarded-Proto $scheme;
> proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
> }
>
> location / {
> allow x.x.x.x;
> deny all;
> proxy_pass http://yourgeoserver:8080/geoserver/;
> proxy_pass_header Set-Cookie;
> proxy_set_header Host $host;
> proxy_set_header X-Forwarded-Proto $scheme;
> proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
> }
> On 03/08/2022 15:58, Christian Mayer wrote:
>
> Hi Frans, hi all,
>
> I had running a GeoServer >2.19 with a nginx in the past. I remember some
> problems with unwanted redirects and similar when behind the proxy.
>
> Besides setting the "Proxy Base URL" I had to set the ENV VAR
> "GEOSERVER_CSRF_WHITELIST", like GEOSERVER_CSRF_WHITELIST=
> my-geoserver.server.de to get the Web-UI and all services fully
> functional.
>
> Not sure if it was exactly the same problems you had but maybe you want to
> give it a shot and report back here.
>
> Best regards
> Chris
> On 03.08.22 08:57, Frans Fierens wrote:
>
> Thx Graham.
>
> This is indeed a solution. But not everything is solved: a wfs/wms
> GetCapabilities request will rely on the Global proxy-base url. It seems
> that the "online resource" option in the wfs/wms service section is not
> being used (?)
>
> To illustrate this:
>
> 1. GetCapabilities using geoserver v2.18.6:
> https://geo.irceline.be/wfs?request=GetCapabilities&service : the xlinks
> are correctly pointing to the proxy url https://geo.irceline.be/wfs. Global
> proxy-base url=https://geo.irceline.be, admin pages are accessible.
>
> 2. GetCapabilities using geoserver v2.21.0 with empty Global proxy-base
> url: https://geonew.irceline.be/wfs?request=GetCapabilities&service : the
> xlinks are pointing to http://georocky/geoserver/wfs and NOT to the
> correct proxy url https://geonew.irceline.be/wfs. This will only be
> correct when the Global proxy-base url is not empty ... but then the
> admin pages are not accessible anymore.
>
> catch 22 ...
>
> best regards,
>
> Frans
>
> On 03/08/2022 02:22, Humphries, Graham wrote:
>
> Hi Frans,
>
>
>
> I lodged the original issue about this. What I have done is set the
> proxy-base url for the workspace and left the Global proxy-base url unset.
> This allows me to access the admin pages.
>
>
>
> *From:* Frans Fierens
> *Sent:* Wednesday, 3 August 2022 2:26 AM
> *To:* Andrea Aime
>
> *Cc:* geoserver-users@lists.sourceforge.net
> *Subject:* Re: [Geoserver-users] problem with Proxy Base URL as from
> version 2.19
>
>
>
> Thanks Andrea,
>
> I already tried to configure the nginx but without success. It would be
> interesting to get more info on the nginx config. There are also other
> issues to deal when using this option: you give internet access to the
> admin pages (which I would prefer not to do).
>
> best regards,
>
> Frans
>
> On 02/08/2022 18:09, Andrea Aime wrote:
>
> Hi Frans,
>
> maybe it just requires a different set up? These two servers are using
> nginx proxying, and a proxy base URL,
>
> but the UI works, as you can see:
>
>
>
> https://gs-main.geosolutionsgroup.com/geoserver/web/
>
>
> http://gs-stable.geosolutionsgroup.com/geoserver/web/
>
>
>
>
> One is a 2.20.x, the other is a nightly build from the developer series.
>
> Unfortunately I don't know exactly how they are set up NGINX wise, but I
> can tell you the proxy base URL configured in GeoServer
>
> is simple, e.g. "https://gs-main.geosolutionsgroup.com/geoserver/
>
