i am running alfresco on linux server i am able to access the files from back end but when running http://mydomain:8080/ it gives the following error
Unable to connect
Firefox can’t establish a connection to the server at mydomain:8080.
The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer’s network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.
tomcat is running but i still cant figure out what could be the cause of the error.
Could you take a look to a tomcat logs?. Maybe you can find more information about the issue.
Could you check compatibility of your amps files with Alfresco version?
Regards,
clv
First, try to hit the Alfresco webapp from the local server itself using curl, like:
curl -v -uadmin http://localhost:8080/alfresco
And see what comes back. If you get a 200 or a redirect, try Share next, like:
curl -v http://localhost:8080/share
If you get a 200 or a redirect then both web applications are working fine and this is due to a network connectivity problem between your client machine and the server or a firewall issue.
If curl cannot hit one of the web applications locally, you should inspect the logs ($TOMCAT_HOME/logs/catalina.out) to figure out why.
You can also "ps -ef|grep tomcat" to make sure Tomcat is actually running, and you can "netstat -atnp|grep 8080" to make sure Tomcat is listening on the port you think it is.
If all of the firewall and networking tests are fine and the logs have no clues, uninstall the AMPs one-by-one until it starts working again.
Related
I am trying to deploy a Nodejs & WordPress website together on an ubuntu server and I am using apache2 for my server config. Everything works fine initially. But after some time my website start showing connection timeout in the browser and when I checked the Ubuntu machine then I found the following:
I checked the error log and increased the worker limit but then got this error again.
I also checked the tasks using htop command then I found this and as I am increasing the worker request number in the apache2 config file the tasks increase automatically.
I also checked which IP calling so many requests and then I found this:
Access logs file :
I have no idea what is going on here and don't know how to fix it. If anyonw know the solution to this problem then please reply.
Thanks
So I'm trying to setup my dev machine to be able to respond to some webhooks, as per the twilio documentation here:
https://www.twilio.com/docs/usage/tutorials/how-use-ngrok-windows-and-visual-studio-test-webhooks
I've got ngrok installed, and have the tunnel up and running, pointing at the port that is specified in visual studio. In this case, 44336.
However, if I go to visit the external URL, I get a very long load time, and eventually a 502 error. Visiting localhost works fine as expected.
So, I tried setting ngrok to point at 8080, and I get a little further along, but still no luck with the following error message in the browser.
With the first tunnel attempt, I can see the GET/ requests show up in the ngrok client, but no error. In the second attempt, I can see the 502 errors:
So I have two questions: How can I diagnose the source of the problem? And how can I setup IIS to accept connections from ngrok?
This is resolved in the latest version of ngrok (at this time 2.3.23).
A related closed issue can be referenced here: https://github.com/inconshreveable/ngrok/issues/448
You can now run:
ngrok http https://localhost:<port> -host-header="localhost:<port>"
for your example:
ngrok http https://localhost:44336 -host-header="localhost:44336"
Just go Right click on project -> Properties, and then disable ssl.
The problem
I'm having an issue where when I start my local dev server with meteor, about 3/5 times the client's socksjs connection via ddp-client.js isn't able to connect and gets an ERR_CONNECTION_REFUSED error. All other connections work fine (websocket, JS, css, etc).
I'm seeing this in the console
The socks is attempting to connect to 192.168.1.14, which is my correct internal ip.
What I've tried
setting the port manually with meteor --port 3000
waiting for Meteor.status().status === 'connected' on the client before making any calls
If you'd like to recreate the problem yourself you can pull down the package I'm working on, ProseMeteor at commit 51c0a304338228102edc75427f72e689a7aafb8a and try running the app yourself by running the bash run_demo script, you should see the problem when you visit http://localhost:3000.
I appreciate any help!
I am running a plex media server for private use on a Ubuntu 16.04 Desktop VM at home. I use it while I'm away on work during the week.
Recently I've been plagued with connection issues. Sometimes it's plex itself that crashes and needs to be restarted and sometimes it's the internet connection (eth0) that needs to be restarted.
I need a little help with a script that I can call via cron to check if the server is remote accessible, if it can reach https://external.address:32400 (please note it only responds to https), if it's not accessible, restart the internet connection (eth0), then check again if it's remote accessible, if it's still not remote accessible then restart the plex media server.
Plex is installed as a service so the call service plexmediaserver restart is how I restart it. I guess as it's a desktop instalation to restart the network the script needs to use service network-manager restart.
I found this post and script but it's very old and outdated.
Hopefully someone can help me out with this.
Thanks in advance.
ok, after doing a little more research on my problems, it turns out I have two different issues, sometimes the VM looses it's bridged connection and sometimes the plex media server crashes.
So, I have split the solution into two simple bash scripts that I call from cron.
The first checks if the internet is working, if not it restarts the VM. Simply restarting network-manager didn't work.
#!/bin/bash
PATH=/opt/someApp/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/$
#Check if the vm can access google.com, if yes then exit
if nc -zw1 google.com 80;
then exit
#If it can't reach google.com restart the vm
else shutdown -r now
fi
The second script checks to see if it can access plex media server locally, if not then it restarts the plex service.
#!/bin/bash
PATH=/opt/someApp/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/$
#Check to see that plex is acessable locally, if yes then exit
if curl -s --head --request GET http://localhost:32400 | grep "200 OK" > /dev/$
then exit
#If not then restart plex service
else
service plexmediaserver restart
fi
Thanks for your suggestions. This is far from an elegant solution, but as I'm pressed for time, it's a solution.
You can use this snippet I found here. You'd put in the IP address you're looking for, and then check the status code against the values found here. If get_status_code returns a code 200, you have remote access.
import httplib
def get_status_code(host, path="/"):
""" This function retreives the status code of a website by requesting
HEAD data from the host. This means that it only requests the headers.
If the host cannot be reached or something else goes wrong, it returns
None instead.
"""
try:
conn = httplib.HTTPConnection(host)
conn.request("HEAD", path)
return conn.getresponse().status
except StandardError:
return None
I have an ASP.NET project (VS2008 on Windows 7 with either webforms, MVC1, or MVC2 -- all the same result for me) which is just the File->New hello world web project. It's using the default ASP.NET development server, and when I start the server with F5, the browser never connects and I get a timeout. I tried to debug this by telnetting to the development server's port while it was running, and I got the same result:
C:\Users\farmercs>telnet localhost 54752
Connecting To localhost...Could not open connection to the host, on port 54752:
Connect failed
I can see in the system tray that the server thinks it's running, and a netstat -a -n command shows that there is indeed an active TCP listener on that port.
This worked in the not-too-distant past, and I could work on web projects using the development server. One thing that has changed since then was that I installed the Microsoft Loopback Adapter to accommodate a local development Oracle installation. I'm not sure this is the problem, but it seems a likely culprit.
I also tried to hit the port using the server name itself (http://mycomputername:54752) but with the same result.
So, what could be blocking me from connecting? And if it's the loopback, then what is a good way for me to retain my ability to connect to my development Oracle server while still being able to use the ASP.NET development server?
have you checked your host file?
%SystemRoot%\windows\system32\drivers\etc\host
look if there is any redirection of localhost or 127.0.0.1 to somewhere else rather than your pc