I followed the docker install on an old laptop running Linux Mint una
Last night I set up DDNS with noip.com and managed to connect to wow (on the same network) using
set realmlist MYNAME.zapto.org
Then this morning I setup my phone as a mobile hotspot and tried again using the same realmlist but no longer from the same network and when i login I get the "Unable to connect..." in the wow client
In the SQL database i changed acore-auth realmlist address to MYNAME.zapto.org (using HeidiSQL, I also changed it in the 'Data' tab)
Related
I am looking to setup AzerothCore for LAN only use.
I am using an ESXi install with an Ubuntu 20.4.3 instance with latest Docker and Portainer for management. I am able to walk through the install process and it works great.
I switched the realmlist in the database to the LAN IP via HeidiSQL, setting both address and localaddress to LAN IP. I have tried just address and localaddress, leaving the other at 127.0.0.1.
I am using a fresh client install and set realmlist there too. I have tried both the dns and the IP, currently set to LAN IP.
I have not touched the compose file or modified authserver or worldserver config files. I am not certain where to look or what to change.
I am able to login with the ID I created all the way to see the Realm, which I select and hit enter. After a short pause the client screen returns to the realm selection screen. Not knowing the backend, I am not sure what is missing now.
I am trying to setup up guacamole in a Digital Ocean Droplet (Ubuntu 18.04). I followed the steps provided in https://computingforgeeks.com/install-and-use-guacamole-on-ubuntu/ to setup guacamole and used Postgresql to authenticate guacamole by following the instructions provided in https://guacamole.apache.org/doc/gug/jdbc-auth.html#idm46227496294336.
The installation got over and I am able to access the webpage at http://droplet-ip:8080/guacamole, but when I try to connect to a remote machine over RDP I get a connection error stating 'The remote desktop server is currently unavailable. If the problem persists, please notify your system administrator, or check your system logs.'
I have checked the login credentials of the remote device, it's hostip and RDP port number, everything is correct. I am able to login to the machine through Remote Desktop Connection in Windows. I can also login to the same remote machine with same credentials in a perfectly working guacamole setup in another digitalocean droplet.
I have also tried this by installing guacamole using docker by following instructions provided in https://wiki.networksecuritytoolkit.org/index.php/HowTo_Setup_Guacamole, but still face the same problem. What am I doing wrong? I would be happy if someone could help me solve this problem
I was finally able to figure out why I was not able to connect to a remote device in Guacamole.
My Digital Ocean Linux droplets had freeRDP already installed. But Guacamole Server 1.3.0 works on freeRDP2. I had to make Guacamole send requests through freeRDP2.
I have enabled SFTP in the connection settings. But somehow the OpenSSH was corrupted in the remote machine resulting in connection error. So, I disabled SFTP. I think guacamole tries to establish RDP and SFTP connection in the very beginning, so even if one of the protocols fail, connection cannot be established. I am not proficient with guacamole so not sure with this point.
After resolving these problems, guacamole was able to send connection request to the remote machine. I checked the status using netstat and the status was SYN_SENT, but there was no response from the remote server. The problem was Firewall.
I allowed the ports for RDP in windows firewall, but the remote machine was in a network which had external firewall. I added the Guacamole Server IP in allowed list for NAT forwarding in the firewall device and finally I was able to establish a connection with the remote machine.
I've been practicing docker and docker-swarm for quite sometime. I had created docker-machine's (manager, worker1 and worker2 nodes) using virtualbox and was able to complete the orchestration
Now, I am trying to repeat the same using Hyper-V (using internal v-switch) in my office, but it hung with the following
ERROR: Waiting for the host
My office desktop has got only one NIC, If I create 'external vswitch' and share it using 'network adapter sharing' I lose connectivity to all my office / client related applications
Hence I chose to create hyper-v 'manager' node using 'internal switch'. I also tried setting up MAT and provided IP address to 'internal switch'. But NOTHING worked
Should I need / create a hyper-v external switch prior creating Internal switch ? Or am I doing something wrong with internal switch setup?
I have a nodeJS server running on my local machine and a Cordova app (hybrid). I am able to connect and run the app using the iOS simulator, however, it does not connect to the nodeJS server on my local machine when the app is installed on my iPhone.
Can you give some hints on how to resolve this issue
Thanks
If you are on the same local network, you can run ipconfig (if on windows) or ifconfig (if on unix) to find out your local machine IP address on the local network.
For example your address may be 192.168.0.2 and your node app runs on port 8080, in this instance you can use 192.168.0.2:8080 to access your server.
An easier and better way would be to use something like ngrok to create a tunnel to your local machine accessible from the internet.
I’m probably doing something stupid here, but....
I can’t access a rails app running on my Mac from a Windows 10 VM. I have set the network adapter to "Share with My Mac". I can access a PHP site running on my mac via http://[my-machine-name].local or http://[my-ip-address]. But if I specify port 3000 to view my rails app I get an error message (to the effect that [my-ip-address] refused to connect) even though the app is running. I don’t know if this is an issue at the Mac end (though my firewall is off for testing), the windows end, or to do with my VMWare network adapter setting. Any assistance gratefully received
Peter
Just use the -b flag while running your rails app like rails server -b 0.0.0.0:3000 so it gets bound to the whole network interfaces and it can be accessed from outside