I am trying to connect to a grpc service in the local computer from grpcui. I am using this command:
grpcui http://localhost:5110
But I am getting the error that there are too many colons in the address.
I have tried too localhost:5110, http://192.168.1.2:5110 (the ip of the compter), and http://127.0.0.1:5110, but I always get the same error.
How could I set the address to can connect?
Thanks.
Related
I have followed the guides at https://www.azerothcore.org/acore-docker/, and everything installs and works fine. Auth, WorldServer, DB, etc all work. However, when trying to play locally (LAN, main computer with client, the server on a different Windows machine on same LAN), it consistently loops back to realm selection.
So, I searched here and found these two questions/answers:
Azerothcore: Looping on Realm Selection List
How to resolve sticking in "Realm Selection"?
I have followed the guide in the bottom one, and have changed the Address field in the database to my external IP address (assigned by ISP). The LocalAddress is 127.0.0.1 The rest of the information appears to be correct.
When trying to connect via the external IP, it won't connect at all. But when I try setting my realmlist to 127.0.0.1 it will connect and log me in, but continually loops back to the realm selection screen.
To make sure it was updating, I changed the name of the realm and it shows up correctly when I try and log in. So the data appears to be saved to the database, but I cannot get it to connect from the LAN.
Followed the official guides, and changed the IP address in the DB to external IP. Same result, except now it takes a few seconds to connect and try to log into the realm. Then fails, back to realm selection.
Help would be appreciated. Thanks.
It's 99.9% related to your networking. That's what it turns out to be for pretty much everyone asking this question.
Most likely either a port isn't forwarded correctly, or your firewall prevents the connection. Try and use an external service to verify if the port is open. (Do a search for "Port open check"). Also, check your firewall to have the worldserver listed as an exception in the right folder.
Another common mistake is to change the "default" values when using HeidiSQL in the realmlist db instead of changing the actual values in the 'data' tab.
We have been using network-scripts to manage the networking of our Linux systems adding NM_CONTROLLED=no in ifcfg-ethn files. But we have encountered a special case where this is not working and we need to use Network Manager service. I have encountered an issue with it.
Existing system IP - > 192.168.2.4/24
Just for testing I tried to configure the same IP on new system and unfortunately, it did get configured. With network-scripts, we never encountered this. It used to check if the IP has already been assigned but Network Manager is not doing this. Do we have any flag or something in NetworkManager settings to enable so that it checks for existing IP addresses before assigning. I have configured it directly using ifcfg-files, and I also need to use virtual interfaces eth0:1 for our specific use cases.
Thank you in advance for your help.
Update 11-08-2021
[eth0-interface]
https://i.stack.imgur.com/n9bCw.png
[eth0:1 interface]
https://i.stack.imgur.com/3Mum9.png
10.133.32.251 already exists in the network, so the network manager is correctly ignoring it after executing the suggested command 'nmcli con modify ipv4.dad-timeout 3000'. But eth0 is also ignored and hence no IP is configured on any interface.
Is it an issue or I am making some mistake here, please suggest
configure ipv4.dad-timeout, for example nmcli connection modify "$PROFILE" ipv4.dad-timeout 3000.
I'm getting the following error when trying to access sites on my server through the browser. I can ssh to the server and I tried running a flush hosts command but that didn't do anything. The host in question is in the mysql user table and has a username/password and all relevant privs. This issue appeared since an office move and the server was switched back on. I can only think it of being a network issue of some sort.
PDOException: SQLSTATE[HY000] [1042] Can't get hostname for your address in db_table_exists()
How do I resolve this?
I think you need to check if the mysql hostname defined in $databases['default']['default']['host'] of the Drupal sites/default/settings.php file is reached by the machine where drupal is running.
Try to connect to ssh and do a ping or a telnet with the hostname.
Instead of the hostname try using the ip address. Otherwise, if the hostname is not resolved, try adding it to /etc/hosts if you're on linux.
I want to bind 2 certificates on a port in my Windows server.
But it doesn't let me add the second certificate once one has already been added for it. Or unless I clear the bindings for the port using netsh delete command.
Adding the second certificate shows this error -
System error 183. Cannot create file when that file already exists
netsh http add sslcert ipport=0.0.0.0:2195 certhash="$thumbprint" appid='{472f53d0-29e1-4cf4-ba9c-79f362d8f6fa}'
Is it possible to bind multiple certificate to the same port?
Thanks in advance.
I have found a solution for this. Surprisingly I didn't find a single resource about this across the web.
It seems that you can't bind multiple certificates if you set the IP as 0.0.0.0 (which I think, is wildcard)
So, for the other certificate, I had to use some other IP.
Since in my case the destination IP address is known and is fixed, which is 17.x.x.x IP address block (Apple) .
So for the second certificate, I changed the ipport in the command to 17.0.0.0:2195.
And voila, it worked!
We have a website/webservice running on one of our servers. We hit that webservice once a day with a scheduled .bat scipt.
Just recently the scheduled task started to fail. The log shows "Invalid URI: The hostname could not be parsed."
When we're logged into the server we can reach the website through http://localhost/website, but get an Invalid URI error when we hit the webservice http://localhost/website/ws.asmx.
Any ideas?
Edit:
We'be tried using the servername, the ipaddress, and port numbers (and combinations therein). Any other ideas?
For the private IP Address your using Wikipedia Reference http://en.wikipedia.org/wiki/IP_address for what are the limits and proper uses.
If you have access to the source code for the web service look for fixed IP Address being used along with having correct Server Bindings for using the service.
Try using the IP Address of the machine instead of localhost.
Basically, I'm taking a wild stab that someone ran a lockdown or a service patch was installed that somehow is filtering request resposes to localhost (127.0.0.1).
Try using the machine name instead of localhost