If I run my .NET core 5 webAPI console app via the exe file, it's listening to all interfaces just as I configured in my appsettings.json
If I run it via pm2, it's accessible only from 127.0.0.1 even though my app logs show it listening to all interfaces.
Why?
The SSL certificate I used was exported from IIS into a pfx file with a password and then imported into the Windows certificates store.
For some reason pm2 didn't like that certificate.
When created a new certificate using Openssl into 2 pem files and used that for my .NET core project, pm2 gave me no problems.
Related
I have a dedicated server running Ubuntu and Rancher Desktop.
I'd like to be able to access the Kubernetes cluster (K3S) from another computer in the same network.
In doing so, after I've setup my kube configuration, I'm getting an error.
Unable to connect to the server: x509: certificate is valid for 10.43.0.1, 127.0.0.1, 192.168.5.15, ::1, fec0::5055:55ff:fe8e:47db, not 192.168.1.8
Passing the following config through to K3S should solve my problem
INSTALL_K3S_EXEC="--tls-san 192.168.1.8"
Reading through Rancher Desktop documentation, I found a potential solution.
Based on the documentation I should be able to pass config through to k3s via the Provisional Script for Rancher Desktop. It is still unclear to me as how I do this for the K3S configurations.
The k3s repository has this issue with a proposed solution at https://github.com/k3s-io/k3s/issues/3369
"SANs should be added to the dynamiclistener cert on demand, based on the SNI hostname requested by the client. Try running the following on the server:"
curl -vk --resolve 172.31.13.97:6443:127.0.0.1 https://172.31.13.97:6443/ping
I am working/learning on web application that has following dependencies:
Express.js + Node.js
MySQL
Angular 4
PM2 (Process manager)
Libs used on the backend:
express
body-parser
jsonwebtoken
bcrypt-nodejs
socketio-jwt
async.js
request
deep-diff
socket.io
cors
mysql
Libs used for the front end
angular2-jwt
socket.io-client
angular-2-dropdown-multiselect
angular2-tree-component
I wanted to know about the usage of CORS, putty for the development in detail for this app.
CORS or Cross-Origin Resource Sharing is a spec that appeared for security reason :
Your browser won't allow you to do http request to another domain except if your server-app return specifics headers (they start with Access-Control-Allow).
The npm cors module allow you to add those headers field in an easier way : app.use(cors())
Putty is a ssh client its permit you to connect to a remote server using ssh protocol (usually you use it to configure your server or run your app on your server).The server need to host an ssh-server like openSSH (nativ on linux).
When I run Tomcat configuration I get the error below.
Unable to open service BOEX140Tomcat.
Here is the error I get when I run SAP Crystal Server management
Here are the installed components of Crystal Report Server:
I would like to know what other software and components I need to install or what configuration changes I need to make .
apache tomcat for bi 4 automatically stop it self
[enter image description here][3]
and changed the config file inside tomcat to below
the apacha bi for tomcat services automatically get stopped in Central Configuration manager.
From your first screenshot, it appears that IIS is active on port 8080. If Tomcat has been installed along with Crystal Reports server and you've used the default port settings during the installation, then Tomcat will be configured to use port 8080 as well.
Only one process can bind to a given port. So as port 8080 is taken by IIS, Tomcat will stop and exit with an error. You can probably find the error message in one of the log files (check the log subfolder in the Tomcat installation folder).
Here's what you can do. Either:
Change the port Tomcat is using (as described here).
Change the port IIS is using (as described here).
Stop the IIS service if you don't need it (as described here)..
I have created a new OpenShift account for a new application I'm developing.
I have added a MongoDB cartridge for the database, and a Tomcat cartridge for the Java web application.
I now need to connect to the database from my Java web app, but I miss two authentication details:
$OPENSHIFT_MONGODB_DB_HOST
$OPENSHIFT_MONGODB_DB_PORT
As far as I know, I have to type rhc env list -a the_name_of_my_app in the console, but my application seems to have no environment variables set.
What can I do?
Apparently, the default enironment variables are visible only via ssh.
In order to see them, you have to type rhc ssh <appid-as-seen-on-openshift-console> followeb by env.
you can see environment variables by doing ssh to openshift. Also you can use openshift port forwarding feature to setup a connection locally to your database.
Openshift blog link for port forwarding
This might be a very simple question for those who are running Mule on linux. I have developed Mule ESB 3.3 app on a windows 8 machine and tested to get desired results by calling my app at
http://localhost:8081/myFlowPath
Now I have deployed same app on to a linux machine behind a firewall successfully but am unable to hit it at http://linuxDomainname.com:8081/myFlowPath. The connection is refused. Am I missing something in configuring mule to run on linux?
We are running Mule CE 3.3 standalone as a linux demon. Do I have to explicitly specify something like the port or hostname in the wrapper.conf? Please let me know. Any help is highly appreciated.
Thanks,
Jenni
You have to configure HTTP Listener host to 0.0.0.0 (change from localhost).
Check log mule at HOME_MULE/logs/mule.log or webservice.log
After deploy your app you must have in HOME_MULE/apps/nameofyourapp/webservice.xml (or filename defined in "config.resources" in file mule-deploy.properties) this:
It work for me. I deploying my mule apps on Ubuntu 16.04 LTS, Mule ESB 3.8.1.
If this not work, it mean that you blocked that port (8081) on this machine (or firewall). Check iptables or another your 3th-party firewall.
Mule handle it easily by using the application properties. Create property files for each environment local|develop|prod.
local.properties
api.host=0.0.0.0
api.port=8080
prod.properties
api.host=127.0.0.1
api.port=9090
Read more about the mule service configuration management at https://docs.mulesoft.com/mule-runtime/3.9/configuring-properties.