Guacamole - server too long period to respond - guacamole

I have a problem with my Guacamole. I installed guacamole on centos 7 from a script I found online and here is the link. When I connect it gives me the error message attached below. However, when I try connecting using SSH from a command line, it works fine. I would be greatful if I can help me out here.
Thanks in advance

Related

Not able to find InitialAdminPassword file after installing Jenkins in Windows 10

Problem: InitialAdminPassword not found.
Question: after I have installed Jenkins on Windows 10 by following the official Jenkins documentation: https://www.jenkins.io/doc/book/installing/windows/, the Jenkins login page is lunched on the browser with localhost port 8080, but it asked for a password which should be found on the following location: C:\Windows\system32\config\systemprofile\AppData\Local\Jenkins\.jenkins\secrets\initialAdminPassword
I'm not able to find this file and the password? any help, please?
Solution:
a simple reboot of the machine solves the issue.
Thanks all.

trouble with neo4j over browser

I have neo4j 3.2.4 installed on a Ubuntu instance. After installing, all I've done to start neo4j is "sudo neo4j console" which directs me to a web interface. Unfortunately, I must connect to the web interface on a different computer which I can do via localhost:7474 or https://localhost:7473. (There is some port forwarding required.) Both get me to the landing page. There I am asked to enter a password (the default one) to connect to the database but I then get the error - "ServiceUnavailable: WebSocket connection failure. Due to security constraints in your web browser, the reason for the failure is not available to this Neo4j Driver ..."
The only site that suggests a solution is here. The suggested solution is to uncomment "dbms.connector.bolt.address=0.0.0.0:7687" in the neo4j.conf file which I did. I then restarted neo4j but I keep on getting the same error.
FWIW - telnet 127.0.0.1 7687 works so connecting to Bolt seems to be fine.
There is also a Github issue referencing this problem but no specific suggested solutions. (Neo4j - issue 504)
Any suggestions greatly appreciated.
Thank you for the information InverseFalcon. FWIW I got things to work by switching over to Firefox where I had also set up FoxyProxy. (So not sure if it was Firefox or FoxyProxy that helped - but would a place to start for anyone else having trouble.)
If you are able to open neo4j web interface, then goto settings -> Network connection section and then check the checkbox that says "Do Not Use Bolt".
After installing the Community edition 3.3.5 on Windows I was getting the same issue as mentioned above, using Chrome. After reading Greg's solution using Firefox, I switched to Internet Explorer and it worked fine.

No acces to jenkins on raspberry Pi 2 (503 no service available)

Good evening.
I hope the question does not exist yet. I searched everything and found nothing suitable for me.
I have a problem with my jenkins that I want to run on my Raspberry Pi 2. I have the setup done as described here:
And it looks like he's running. But I do not get access to it via browser.
If I want to connect with http://192.168.2.XXX:8080, I get the message "Error 503 Service not availabele". But the Jenkins is running when I look at jenkins status. What am I doing wrong? :-(
Hope Someone can help

Jenkins 2.5 installation error (An error occurred during installation: Forbidden)

I have a fresh CentOS box, installed Tomcat 8.0 and Jenkins 2.5. After entering the secret key for a brand new installation, the next step Install suggested plugins or :Select plugins to install:. After clicking on Install suggested plugins I got an error saying
An error occurred during installation: Forbidden
I assume is related to folder permissions, the question is which one?
UPDATE: The jenkins log says
Found invalid crumb a711b93261896fb36a1d6ffbe163dca6. Will check remaining parameters for a valid one...
May 21, 2016 4:19:34 AM WARNING hudson.security.csrf.CrumbFilter doFilter
No valid crumb was included in request for /jenkins/administrativeMonitor/hudson.diagnosis.ReverseProxySetupMonitor/test. Returning 403.*
Thanks in advance.
If it's any help to anybody, I "fixed it" by restarting Jenkins http://jenkins:8080/restart, or whatever protocol, domain, and port. Then when I went back in it asked me for the secret key again, and then installed all the plugins successfully.
I have faced this problem before. It was because I was using a VPN. Once I closed the VPN, everything returned back to normal.
I was getting the same error when I was using Internet Explorer for JENKINS INSTALLATION on Windows 2019. I installed Chrome before trying again and the error went away!
I was facing this issue because I was using Internet Explorer. Switching the browser fixed the issue for me.
I faced this same issue, Alex's answer helped me.
Here's some addition to it:
I was running Jenkins on docker, so to restart it I had to do the following;
List all the running docker containers on the server:
docker container ls
Copy the container id for the Jenkins container
Restart the docker container for Jenkins using its id:
docker restart <jenkins-container-id>
Visit the URL for Jenkins again:
http://your-url:8080
Input your initial admin password, and then try setting up Jenkins again.
That's all.
I hope this helps

Wildfly error: Could not start http listener

I'm new to Wildfly and I hope you guys can help me with this problem:
I'm following this tutorial on how to Install Wildfly 8 and when I'm trying to execute step 4 I get the following errors:
I've been googling for a while now and I can't find an answer. I've tryed with JDK 7 and 8, no changes, I'm using admin permissions, I've even tried to download Wildfly again and still no changes.
More experienced co-workers have seen this and don't have a clue about what's going on.
Can you help me? Thanks
The tutorial you linked to, has Wildfly configured to use the default port 8080. Most likely, you have another process or service running which is already using port 8080. Try to find out what process it is and stop it, or try configuring Wildfly to use a different port.
try restart the machine or enable IPV6 in the machine, this error will be resolved
Those having the same problem should check who else uses the port 9990 in your Windows system. TCPView is a good tool to find out the guilty of charge. One of possible common causes in this case is NVIDIA Network Service (NvNetworkService.exe).
If that's the case just find it in your Windows services list and stop/disable it. The service itself is responsible for checking for Nvidia drivers updates, so any time you want it back just turn it on manually.
In my case, I inadvertedly added an AJP socket binding while using standalone jboss_cli utility:
[standalone#localhost:9990 /] /subsystem=undertow/server=default-server/ajp-listener=ajp:add(socket-binding=ajp)
This led to an 'already in use' error that doesn't let any app to start and signaled 503 error through an Apache web server.
I deleted the binding:
/subsystem=undertow/server=default-server/ajp-listener=ajp:remove
And then everything worked normally.
I too had the same issue.After analysis it was found that the SSL port(443 in my case) was creating this issue. I just terminated the processes that were running on 443 and restarted the wildfly and everything worked fine after that.
I had faced same issue with wildfly_8.2.1
Port 8080 was also free, so that solution doesn't worked for me.
Try below procedure as it helped to resolve my issue.
add below lines to your server's /etc/sysctl.conf file
net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
No restart is required for this solution.

Resources