I am looking for good references for setting up Nginx: for a Java (J8EE) app running in Wildfly18(+Adapter)[Set up as service] talking to local Keycloak9(Wildfly)[Set up as service] on Linux (Ubuntu).
This will be a simple setup (No clustering etc.) and can even use LetsEncrypt if required.
Works locally on W10; and have set up mostly on an ubuntu server; but serve, now being remote, is making things more awkward.
Any references greatly received.
I have done the NGINX (using letsencrypt) and posted it here.
There was a realy horrid problem then with "invalid redirect uri" problem and this post also have the "solution" to that.
See:
Moving to https in keycloak using nginx
Related
As a part of a project, setting up the litmus Chaos portal on the local machine is one of the requirements.
I could run the litmus Chaos frontend on on the localhost by following the below link: https://github.com/litmuschaos/litmus/wiki/Litmus-Portal-Development-Guide
In the above case we are starting the backend servers using kubectl commands.
But I am facing issues to set up my local environment such that I ll be able to start the backend servers on my local IDE(intellij for instance) without using kubectl commands.
It would be great if anyone could help me with this. Thank you in advance.
Good afternoon everyone,
I have the following setup in my home-lab:
ESXi
PfSense
NextCloud
TrueNAS
I am running HAproxy in PfSense instance, and have a domain that I have set up to access my NAS locally (and I have tested it and can make it work externally, though I do not want to do that). I can access it localy at an address like nas.homelab.com
I am trying to set up NextCloud the same way, this time externally, however, I keep getting a 503 error. I have this set up so I can see it from the internet as well, using a link similar to nc.homelab.com
I've gone through and set everything up as best I can using a Lawerence Systems video on the subject, however, I can not figure out how to get rid of the 503 error.
I've seen other threads mentioning to make sure I have a default backend to eliminate this error, however I have one set for the NAS, since I know it works, and nothing has changed.
Thank you all for your help!
Sam
I'm having trouble trying to side-load an add-in in MS Word, getting the error
'ADD-IN ERROR: A problem occured while trying to reach this add-in.' The add-in needs to be hosted on a local docker environment to be integrated in the rest of a web aplication.
Setup
The add-in files are hosted on a local docker machine, accessible through both an ip-address and a https://dev.local address. The add-in is reachable through Internet Explorer and Edge Chromium without any certificate errors. It doesn't matter whether I try to reach the IP address of the locally mapped dev.local, the add-in refuses to load and just crashes. I'm on Word version 2002 build 12527.20194. Another word-addin that we host externally works fine.
What i've tried
I've been messing around with the settings in Internet Explorer (moving the sites to local zone, trusted zone, enabling and disabling the protection there).
I've upgraded Edge to edge Chromium. I've tried to use the Preview of
Edge Developer Tools, but that crashes when the error occurs.
I've tried using Fiddler and activate the runtime logging, but can't get more information on what's going wrong.
I've used the Yoman validation on the manifest.xml and everything checks out.
I've also enabled loopback through CheckNetIsolation LoopbackExempt -a -n="microsoft.win32webviewhost_cw5n1h2txyewy"
I'm pretty much at a loss now: what can I do to get more information on what's crashing the add-in?
OK so I managed to finally get this to work, leaving this here for anyone who might run into the same issues.
Because the local sideloading did work, I figured we needed to emulate the localhost situation with the docker. So I instructed the virtual machine to forward localhost:3000 to the Docker Toolbox port 443. I also copied over the SSL certificates generated by Yoman in <userhome>/.office-addin-dev-certs to the Nginx docker and instructed Nginx to use those SSL certificates for port 443.
I'm not entirely sure if adapting all of the other settings (such as enabling the loopback interface and using the about:flags page to always allow https on localhost are also neccesary, maybe just emulating the webserver on localhost is enough. Hope this helps someone!
I am trying to document a server and replicate its setup done by another person. Server is running Play Framework which also acts as a reverse proxy to MediaWiki running on Apache on the same server on a port that is not open externally on the server.
The Play Framework routes requests to the Media Wiki Server using ScalaWS. When I check the request it creates a request by using the server domain with the Apache port and the media wiki file.
In the real server it is working fine but in the test deployment it fails to reach mediawiki. It works if in the test deployment I open the Apache port externally.
So Somehow the request to the local server running internally on the machine needs to be accessed without routing the request externally. How can this be done? If anyone can give some quick tips or things I can check or even explain how this may be working, that would really help save me some time.
The /etc/hosts file had the wrong domain defined. Fixing that fixed the problem.
I have tried to find info on this, but can't seem to find what I am actually looking for.
I have a server running plesk. What I would like to do is set it up so that I can run my browser through that and have a static IP address. Is this possible and if so, any pointers on how to set this up?
I know that this is a few years old, but in case someone stumbles upon it. It's quite easy now with Onyx and Docker.
Create a new Docker instance with robhaswell/squid-authenticated.
Configure as follows:
Yes, you just need to install proxy server like squid or tinyproxy or 3proxy
Also as a more simpler but with more limitations you can create a domain and use one of PHP proxies like this one or this one
Don't forget about authentication.