There was an error setting up your hook: Sorry, the URL host localhost is not supported because it isn't reachable over the public Internet. While adding webhook getting this error.
You are using a local ip address. If you run ipconfig or ifconfig, you see the "local" ip address.
Github needs your public ip address. For example go to https://whatismyipaddress.com/ and it will show your public address. If you're running Jenkins on localhost:8080, then Github needs http://myPublicIP:8080 as the url. Then you have to forward the port 8080 on your router to the computer running Jenkins.
Related
I am installing a server using IIS 7, and I succeded to install it, and access it by localhost:80 or [my IP]:80. But when I use my smartphone, when I access to [my IP]:80, I get "localhost refused to connect: ERR_CONNECTION_REFUSED". What should I do to solve this error?
I tried to restart IIS, but it didn't work.
I tried to check the log file, but there was no error.
According to your description, I guess you may not add the ip address binding for your router.
I suggest you could try to add the both public ip and vitual ip into the binding and make sure your domain is right.
More details about how to add the binding, you could refer to below image:
I would like to deploy a container based app in azure container service, and followed this tutorial.
https://learn.microsoft.com/en-us/azure/container-service/dcos-swarm/container-service-mesos-marathon-ui
Everything went well except that the public url is showing
ERR_CONNECTION_TIMED_OUT in browser.
When pinging the url, able to get the IP address but pings are showing as timed out.
I have verified agents LB with port 80 as allowed in the rules list.
How to access the application through public web ?
When pinging the url, able to get the IP address but pings are showing
as timed out.
Azure disable ICMP package, so you could not ping Azure public IP address. You could use telnet or tcping to check whether your service is listening.
Do you bind port 80 of the container to port 80 of the DC/OS agent? If I don't do this, I get same error log with you. Please refer to this link.
Note: I test in my lab, if I did not do this, nginx service will listen on other port. I ssh to the agent VM.
root#dcos-agent-public-65818314000001:~# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
7e8091548413 nginx "nginx -g 'daemon off" 14 minutes ago Up 14 minutes 0.0.0.0:4912->80/tcp mesos-d7be0314-6be2-467b-8376-433a05033b17-S1.42edeac0-2aa3-4ecd-acaa-17d5f2f4ac19
The service is listening on port 4912 not 80.
If you do this step, I suggest you also could ssh to agent VM(same user name and private key) and execute docker ps .
I follow the steps on the below link, and build it on my ubuntu cloud, it seems ok, but not working on my browser.
https://mayan.readthedocs.io/en/v2.1.4/topics/installation.html
no matter on local: http://127.0.0.1:8000/
or on my cloud server: http://*..55.12:8000/
Can anyone help? I found less information on the internet about this EDMS.
The address 127.0.0.1 (or localhost) is a loopback address and only accesible to the same host only.
From the installation instructions:
Note that the default IP address, 127.0.0.1, is not accessible from other machines on your network. To make your test server viewable to other machines on the network, use its own IP address (e.g. 192.168.2.1) or 0.0.0.0 or :: (with IPv6 enabled).
use:
./manage.py runserver 0.0.0.0:8000
Installation instructions
I have Two Linux Machine Redhat & Centos Under Window 7(as host) In Vmware Workstation.
I configure DNS server & DHCP Server in Redhat(10.0.0.1).
Client which is Centos is able to get IP(10.0.0.30) from DHCP server but it is not picking up name from DNS Server.
Problem is At server 10.0.0.1 i am able to ping itself by hostname like
root#server->ping server.example.com Ping successfull
But Client is not able to ping Server by Hostname like
root#localhost->ping server.example.com Ping Not Successfull
Client is able to ping Server by its ip like
root#localhost->ping 10.0.0.1 Ping Successfull
Now My questn is that Why Client is not able to ping server by its hostname & why client is not picking up name from DNS server,
Just had similar issue on my Debian VM running on a Win7 host.
Setting up DNS server isn't enough to resolve server name, especially when proxy is used in your network environment.
To solve it, you've to export http_proxy environment variable on command line before calling other executables. For example:
export http_proxy="http://{your proxy ip address here}:{your proxy port here}"
As usual, remember to add it to your profile script so you don't redo it after each boot.
I'm following the Micro cloud Foundry Quick-Start guide here:
http://support.cloudfoundry.com/entries/20316811-micro-cloud-foundry-getting-started-guide
I'm on step 10: registering a new user and I'm not able to connect:
$ vmc target api.lsmith.cloudfoundry.me Host is not available or is
not valid: 'http://api.lsmith.cloudfoundry.me' Would you like see the
response? [yN]: y HTTP exception: Errno::ECONNREFUSED:Connection
refused - connect(2)
My VM is in NAT mode. The Current Configuration in my VM is listed as:
Current Configuration: Identity: lsmith.cloudfoundry.me (ok) IP
Address: 172.16.x.x (network up)
When I run the host command in my console I get:
$ host api.lsmith.cloudfoundry.me api.lsmith.cloudfoundry.me is an
alias for lsmith.cloudfoundry.me. lsmith.cloudfoundry.me has address
127.0.0.1
I'm not able to reach the vmc target in my browswer but when I visit http://172.16.x.x/info I get:
VCAP ROUTER: 404 - DESTINATION NOT FOUND
I think this is a DNS issue but have no idea what I need to do to fix it. I tried changing the nameserver IP in my /etc/resolv.conf from 127.0.0.1 to 172.16.x.x but that didn't work.
I was able to resolve this by reconfiguring my domain (option 4 in the VM) using a newly generated domain token at https://micro.cloudfoundry.com/dns