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.
Related
I have been struggling a bit to get access to airflow from outsite my network.
I have airflow running on a raspberry pi 4, and all seems to be working just fine, I can access it via http://localhost:8080.
I have also set forwarding rules in my home router pointing to the raspberry pi:
The port forwarding is working since I can see it open using an external tool, and I have also set up a SSH port forwarding to access my raspberry pi from outside my local network.
So accessing http://my-public-ip:123 should be taking me to my aiflow web ui, but instead I just got "This site can't be reached".
Can anybody spot what I have done wrong or if I skipped any step of the process?
Thanks in advance.
Are you running Airflow with Docker or you have it installed? If using Docker, setting the webserver's service port to 127.0.0.1:8080:8080 it's the first step.
Secondly, you might need to look into the config webserver options. You will need to set the AIRFLOW__WEBSERVER__BASE_URL: 'http[s]://your_address/airflow' environment variable and install a reverse proxy (I suggest you nginx); you can find more details here. After you've done this, don't forget to also set the environment variable AIRFLOW__WEBSERVER__ENABLE_PROXY_FIX: 'true
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 have created a script which is running on a localhost and port:5006 on EC2 instance. I am planning to make it run in the background even after I logout from SSH terminal. The question is that when I try to throw or reach to my script from my browser or Postman with the following link:
http://ec2-52-15-176-255.us-east-2.compute.amazonaws.com:5006/main?<myparametes>
Steps which I have done is:
1.) Created EC2 Instances of Linux flavor (Which is available in Free tier)
2.) Started the python script in virtualenv folder and listening to the port,
3.) Now trying to reach the IP and the port as mentioned above!
Apart from that, I haven't done anything else!
Please help me with understanding the concepts because there are no such tutorials available which serve straightforwardly
Agreed that the question is very broad, so starting from a basic step: have you created the proper security group for your instance that allows this 5006 port to be accessible from whichever network you are trying to?
I am trying to deploy my jhipster app on DigitalOcean.
I have already created a droplet, connected to it with ssh and cloned the jhipster app from git. Now im having trouble with running the app on the server.
I can run the app on localhost, but I want to create remote access to it.
As i have never done it before I would like some help on how can I achiave that.
Thanks in advance!
Solved my problem.
Didnt have to configure anything, just had to write in the url: ip adress of the virtual machine + : port number and it worked.
e.g:
http://xxx.xx.xxx.xx:8080
I've recently upgraded an on premise Service Fabric cluster to 5.1.156.9590 running on Windows Server 2012 R2. I removed the original cluster and created a new one. Unfortunately my new cluster doesn't seem able to create the firewall rules for any ports specified in the service manifests. The only warning I see that seems connected is this from the ServiceFabric Hosting:
Did not enable firewallpolicy for current profile 1
I can't find any help regarding this message. I'm wondering if something has changed as regards specifying ports for a service or there's something on the node boxes that I haven't configured correctly.
Any pointers appreciated as I'm sure I didn't have to open them manually previously.
Unfortunately, I had the same problem and didn't succeed in reanimation of Service Fabric. Only moving to Azure helped to resolve the issue. You can try next things:
Completely remove SF, SDK, related services, firewall rules and directory SFData on C drive, then install everything again.
Check that firewall is enabled
Check that SF service is created and able to start
If the service is not able to start, check events, there is a special folder for SF where you can find additional and detailed infromation
If you have customized the address on which listeners will listen in SF cluster config, try to change it on something different and see if SF would deploy or not