I have a Dockerized R Shiny app on Google Cloud VM. It was running well but from yesterday I am not able to access the shiny server. I have checked the docker logs and it gives me below message:
**[2019-03-13T14:56:11.496] [INFO] shiny-server - Shiny Server v1.5.7.890 (Node.js v8.10.0)
[2019-03-13T14:56:11.498] [INFO] shiny-server - Using config file "/etc/shiny-server/shiny-server.conf"
[2019-03-13T14:56:11.559] [WARN] shiny-server - Running as root unnecessarily is a security risk! You could be running more securely as non-root.
[2019-03-13T14:56:11.562] [INFO] shiny-server - Starting listener on 0.0.0.0:3838**
So, does it means the shiny server is running? If YES then why I am not able to access it from a browser (on the browser it gives me an error ERR_CONNECTION_REFUSED)?
Note: The port 3838 (default shiny server port) is whitelisted from VM.
Related
I have deployed a vue 3 vite project on digitalocean app platform. The build process completes with no error but deployment fails with the error below
From the delploy logs, I see that the app is being served on port 5050
But both my run command npm run preview --port 8080 and app HTTP port is also set to 8080
Why is the app being served on port 5050 instead of using 8080?
Out of nowhere one of our API servers has started to fail with the following error:
http: TLS handshake error from 172.23.88.213:17244: EOF
It throws this error for every single node in the cluster, thus failing to start. This started happening this morning with no changes to any infrastructure.
Things I've tried that haven't helped:
Manually restart the weave docker container on the master node.
Manually kill and reschedule the api-server.
Manually restart the Docker daemon.
Manually restarted the kubelet service.
Check all SSL certs are valid, which they are.
Check inodes, thousands free.
Ping IP addresses of other nodes in cluster, all return ok with 0 packet loss.
Check journalctl and systemctl logs of kubelet services and the only significant errors I see are related to TLS handshake error.
Cluster specs:
Cloud provider: AWS
Kubernetes version: 1.11.6
Kubelet version: 1.11.6
Kops version: 1.11
I'm at a bit of a loss as to how to debug this further.
I am running Artifactory Pro (5.3.1), and was trying to use the docker registry functionality.
I created a docker repository, and gave it a port 5001 in the "Registry Port" config.
However, there's nothing running on port 5001 ("telnet localhost 5001" refuses to connect), and the logs show this:
[http-nio-8081-exec-7] [ERROR] (o.a.s.s.SshAuthServiceImpl:210) - Failed to start SSH server
java.net.SocketException: Permission denied
at sun.nio.ch.Net.bind0(Native Method) ~[na:1.8.0_72-internal]
at sun.nio.ch.Net.bind(Net.java:433) ~[na:1.8.0_72-internal]
at sun.nio.ch.Net.bind(Net.java:425) ~[na:1.8.0_72-internal]
at sun.nio.ch.AsynchronousServerSocketChannelImpl.bind(AsynchronousServerSocketChannelImpl.java:162) ~[na:1.8.0_72-internal]
at org.apache.sshd.common.io.nio2.Nio2Acceptor.bind(Nio2Acceptor.java:66) ~[sshd-core-0.14.0.jar:0.14.0]
Any idea what could cause a "permission denied"? There's nothing running on that port (same error for any other port). It's on Ubuntu 14.04.
I had a misunderstanding how the docker registry worked with Artifactory.
The Artifactory service doesn't actually open the port assigned to the repo (5001 in this case), but the reverse proxy will listen on it and forward it (with the right X-forwarded-port) to the "normal" Artifactory service port (e.g. 8081).
After setting up the reverse proxy for it, it worked fine.
After installing Nginx and letting SonarQube running in background, also configuring the conf.d file from nginx I am just getting a 500 error.
https://docs.sonarqube.org/display/SONARQUBE52/Running+SonarQube+behind+a+Proxy
What Am I missing?
I am having an issue deploying a shiny app via shiny-server on ubuntu 14 (on chromebook).
I followed all of the setup steps for shiny-server, and the app appeared to deploy OK on my computer.
I run sudo shiny-server in the command prompt and this appears:
[2016-01-10 14:52:36.348] [INFO] shiny-server - Shiny Server v1.4.1.759 (Node.js v0.10.40)
[2016-01-10 14:52:36.351] [INFO] shiny-server - Using pidfile /var/run/shiny-server.pid
[2016-01-10 14:52:36.352] [INFO] shiny-server - Using config file "/etc/shiny-server/shiny-server.conf"
[2016-01-10 14:52:36.410] [WARN] shiny-server - Running as root unnecessarily is a security risk! You could be running more securely as non-root.
[2016-01-10 14:52:36.414] [INFO] shiny-server - Starting listener on 0.0.0.0:3838
I run the command sudo ifconfig to get my server IP address, and the site runs on my computer at: http://my_ip_address:3838/sample-apps/hello/.
However, when I try to go to this link at another computer in my house, the website does not load.
Note*: The thing I did to try to fix it was to configure my server's firewall to allow inbound TCP connections on port 3838, which I think Idid.
When I type sudo ufw status into command prompt, I get:
Status: active
To Action From
-- ------ ----
3838/tcp ALLOW Anywhere
3838 ALLOW Anywhere
80 ALLOW Anywhere
3838/tcp ALLOW Anywhere (v6)
3838 ALLOW Anywhere (v6)
80 ALLOW Anywhere (v6)
I am not sure what else to try.
Have you tried
my_ip_address:3838/hello/
instead of
my_ip_address:3838/sample-apps/hello/
If you check the content of /etc/shiny-server/shiny-server.conf and it says directory_index on; you should be able to browse to my_ip_address:3838 and see a directory listing and at least a welcome page.