I'm Unable to access CouchDB remotely. I'm using a Windows 2008 virtual machine in Azure.
I did the following,
1) Installed IIS on windows server 2008.
2) Created an endpoint for port 5984
3) Installed CouchDB & verified the same by using futon
http://127.0.0.1:5984/_utils
4) Created a subdomain ( db.mydomainxyz.com ) with my domain registrar & verified. If I type http://db.mydomainxyz.com/ in browser - IIS7 default page gets displayed.
5) Made couchdb to listen on all network adapters by setting => bind_address = 0.0.0.0
6) Created vhosts to point to my domain = > db.mydomainxyz.com:5984 = /db/_rewrite/
After doing all these things I'm still unable to access CouchDB remotely http://db.mydomainxyz.com:5984/
Is there anything I'm missing ?
After changing the bind_address, CouchDB must be restarted. The problem is that its daemon is very resilient. So even if you tried to restart it, it probably never stopped. Restart your virtual machine instead.
See the similar discussion on ServerFault for more information.
This command solves the issue:
netsh advfirewall firewall add rule name="Apache CouchDB" dir=in action=allow service=any enable=yes profile=any localport=5984 protocol=tcp
Related
does anyone know what i'm doing wrong here? i'm trying to access my windows-server 2019 ec2 node locally so i can successful collect metrics via WMI Exporter and point this at my prometheus instance.I'm trying to access port 9182 for WMI Exporter, and can connect fine via localhost on my remote widows instance, also the IPv4 Address on the same instance.I've also tried to configure the firewall port on the windows host 9182. When I try to access via localhost this returns This site can’t be reached, if i try via public address on both i get Can’t reach this page. Ive opened port 3389 inbound and all traffic ipv4 outbound. Any help would be great. I have also tried adding RDP Ip directly to the inbound security rules, yet still have the same issue. Many Thanks
After installing windows_exporter, the installer will create an inbound rule for windows_exporter itself. However it may be not enough and cause your issue for some reasons. See this similar issue.
Try to add a new inbound rule for the Windows firewall and let any programs can access the listening port (default 9182). That works for me.
Trying to host a web site on my local Win 10 Pro machine withing IIS, provided I share the IP to my friends. My host file contains something like:
127.0.0.1 site1.com
127.0.0.2 site2.com
127.0.0.3 site3.com
127.0.0.1:1 site4.com
127.0.0.1:2 site4.com
123.45.5.6 site5.com
123.45.5.6:33 site5.com
They all work as expected except for the imaginary external ip (only for example), and adding the port or not makes not difference. Seems i've tried what makes sense, say my external is '1.2" Creating a host entry like
1.2 # or
1.2:Port # the external IP with port
Also attempted adding an exclusion for he firewall to help ensure the traffic is allowed by doing:
netsh advfirewall firewall add rule name="Open Port" dir=in action=allow protocol=TCP localport=81
Kind of lost what might be missing, any suggestions?
Thanks for he help.
First. There is no need to add port after IP address in hosts file. Port can be configured on IIS by setting binding.
Second. If you want to allow any web client can access the site host on local WIN10 pro, you need to make sure WIN10 pro and web client are in the same LAN. Otherwise it is need to buy a public domain and bind to WIN10 pro device.
Using Ping command is a great way to test traffic between devices. It can help you make sure if web client can create connection with WIN10 pro.
I have several sites on hosted on my local iis that I cannot access all of sudden.
Error I'm getting in all browsers I have installed (Chrome, IE, Edge) is- server DNS address could not be found.
Last thing I was doing before things wend wrong- installing Web Deploy 3.5, but uninstall did not help.
I checked hosts file and bindings in iis- both are valid.
Another thing I've tried with no luck:
Reset WINSOCK entries to installation defaults : netsh winsock reset catalog
Reset TCP/IP stack to installation defaults : netsh int ip reset reset.log
Flush DNS resolver cache : ipconfig /flushdns
Renew DNS client registration and refresh DHCP leases : ipconfig /registerdns
Flush routing table : route /f (reboot required)
Ping cannot file host as well
Ping request could not find host XXX. Please check the name and try again.
At the same time htt://localhost shows Default Web site with IIS welcome page.
This appeared to be a problem with permissions on host file- somehow those got broken
We have CouchDB installed on a separate machine.
When it was installed on my machine, it was accessible through Fauxton via link http://localhost:5984/_utils/index.html
Also, I am using Divan, a C# library to interact with CouchDB. It uses host as localhost and port as 5984 - default host and port names to connect with database.
But now I have CouchDB installed on another machine, how can I access it in this case?
Please suggest.
Thank you.
You need to allow exterior access in the new machine (which I'll just call the server). Your computer is the client. First, make sure the server is accessible from your network and get its IP address using ipconfig or ifconfig in the command line.
First, in the server, open the CouchDB configuration file, which is
/usr/local/etc/couchdb/local.ini in Linux
or
C:\Program Files\CouchDB\etc\couchdb\local.ini in Windows
and change
[httpd]
bind_address = 127.0.0.1
to
[httpd]
bind_address = 0.0.0.0
If there is no bind_address already in the file, just add it.
Then save the file.
Now, from the client, you can access futon from your machine using {SERVER_IP}:5984/_utils.
In Divan, set host to {SERVER_IP}. Unless you configure it otherwise, the port remains 5984.
Reference:
http://docs.couchdb.org/en/2.0.0/config/intro.html *
http://docs.couchdb.org/en/2.0.0/config/http.html *
(*) I'm assuming you're using CouchDB 2.0, but in my experience with 1.6.1 this instructions also work.
Connect to your server locally:
localhost:5984/_utils
then simply from the setting section, change the bind_address to 0.0.0.0
I've stopped my virtual server and then started it.
after restart i lost the ability to access remotly to my server (rdp).
i have the needed end point for remote access but is still not working.
i have tried to :
1) delete end point and re-create it.
2) scale up my server forward and backward.
still it look like it can be two things:
1) rdp service after server start is down
2) no firewall rule is created.
notify that after server was started it's IP Address was changed!!!
Thanks
Use server name not IP, as IP may change.
Make sure that you use external port specified in the endpoint.
Make sure that your private port is set to 3389.
Make sure TCP is selected as the protocol.