How can I run the standalone version of Cloud9 over a secure connection (HTTPS)?
Related
I have been running a dotnet webapi project. I just changed my machine. On my old laptop HTTPS was working fine in my local development. But now that I have changed my machine my browser does not trust the localhost server certificate. I have tried running dotnet dev-certs https --trust but it did not work. My old and my new machine are running on Windows. Any help?
Can DC/OS run on in an offline environment?
After a successfull installation in my offline environemnt the login web screen would not open with the following message:
The server refused the connection.
I had to disable authentication in my cluster because Im running it in a private offline network.
Just add the following line in genconf/config.yaml before custom installation:
oatuh_enabled: 'false'
this way authentication needed.
https://dcos.io/docs/1.7/administration/opt-out/
I implemented SonarQube on the server, and I do most of the configurations remotly. Hence whenever a plugin is installed, a restart of SonarQube is required and every time I have to explicitly (manually) restart the SonarQube server.
Is there a way to restart SonarQube remotely?
For example, like jenkins through http://sonar_url/restart.
Since SonarQube 5.4, you can restart it directly from the UI (Administrators should be able to request a server restart from web console) or using the WS /api/system/restart (WS /api/system/restart should trigger a true restart of SQ).
POST api/system/restart
Since 4.3 Restart server.
Available only on development mode (sonar.web.dev=true).
Ruby on Rails extensions are not reloaded
Regards,
Michel
In my SonarQube instance (v5.6), I use the below curl command to restart SonarQube server
curl -u username:password -X POST https://SONAR_INSTANCE/api/system/restart
I have a simple sinatra app running on an AWS windows instance. Running the application from the localhost works fine (i.e. http://localhost:4567), but I am unable to run it remotely.
My AWS windows instance is available to me from remote as I am able to connect to it using RDP.
After reading some other similar issues, I have already applied the following:
My AWS security group is opened for port 4567 (I actually also opened it for any inbound connection just to see if that will solve the issue - it didn't)
I tried running: ruby my_sinatra_app.rb -o 0.0.0.0
I tried running: ruby my_sinatra_app.rb -e production
I tried adding to the application itself the following code: set :bind, '0.0.0.0'
I am still unable to run the application remotely. Any idea?
I was able to solve my issue, so for the sake of completeness I am publishing the answer.
This wasn't a Sinatra issue, but an AWS issue (maybe not really an issue, more like my misunderstanding). I was under the impression that updating the AWS security group for opening the 4567 port will do the trick.
However, it turns out that I needed also to open the port on the Windows Firewall on my Windows AWS instance. After opening the port on the Windows Firewall I was able to remotely connect to my Sinatra app.
I have a production LDAP server running on 389 and I want to install another OpenLDAP for test purpose on port 10389.
I am wondering how to install the OpenLDAP daemon as a windows service that will run on another port than 389.
Note: I cannot use the slapd install as I already have this service installed...
Well, I installed NSSM that can run any kind of executable as a service.
I have created a batch file with the appropriate options and now I have Open LDAP running as a service on a non default port.