So, long-short story:
I tried to install azerothcore with mariadb and it's not working. Do not even try to do that :))
Then I have reinstall the server, and sterted to install azerothcore on ubuntu 20.04 with mysql 5.7, php 7.4, and phpmyadmin - VPS. External server.
After I made everything well, and set up a new account with gmlevel, updating the realmlist (address tab) from table with the new external IP and set the BindIP with the VPS IP, I can not connect to the server from the client.
I have deleted the conf file from WTF folder (client). I do not got any errors in terminal, everything it's seems to be fine. Also, the 8085 and 3724 ports are open when I start ./authserver and ./worldserver.
What do I forgot? Any ideas?
realmlist table
Related
Since a day or so I can not access the databases on two of my servers any longer
I use
mysql -h host.sld.TLD -P 3306 -user user
which I have configured to allow my user from my host without password
but get the above error.
However, when I use
telnet host.sld.TLD 3306
I get
5.5.5-10.8.5-MariaDB-1:10.8.5+maria~ubu2004(si4cyW'Y��-n;{ypDA\)VU)mysql_native_passwordC
I am using homebrew's mariadb (currently 10.9.3) on my machine, which I can reach from the outside. One each of the 'failed' remotes is on ubuntu with 10.8 and one on a Mac also with 10.8, and outgoing works from both. OpenSSL is version 1.1.1s on both Macs
I have installed a number of different mariadb versions all have the same issues, as do their perl libraries. mysql itself works.
What am I doing wrong here?
This issue has been fixed in MariaDB 10.9.4 which was released yesterday. Brew still offers 10.9.3, usually it takes a couple of days until latest 10.9 release will be available via brew.
The issue doesn't affect the server itself, but Connector/C and command line tools which link against Connector/C.
See also: MariaDB connector in Python cannot connect to remote server
Scenario:
Current server # example.com is running an older version of amazon AWS Lightsail with wordpress (ubuntu) and we just had a new certificate issued using letsencrypt. All is well. Original cert was requested with wildcard, so functional for any subdomain.
Now, we needed to spin up a fresh new server for a subdomain, let's call it development.example.com.
The new AWS lightsail instances now are no longer Ubuntu but Debian!
The idea was to install certbot in the new Debian instance and then copy over the certificate files from the primary server # example.com.
I've done this successfully in the past when it was going from Ubuntu to Ubuntu but now that the new instance is Debian, the Really Simple SSL plugin does not recognize that a certificate is installed.
STEPS I took to move the certificate files:
What I've done before is simply to copy /etc/letsencrypt/* from one server to another and then follow the steps outlined in the AWS documentation here:
https://lightsail.aws.amazon.com/ls/docs/en_us/articles/amazon-lightsail-using-lets-encrypt-certificates-with-wordpress#complete-the-prerequisites-lets-encrypt-wordpress
In this case, performing the steps 7.4, 7.5, 7.6 and section 8.
However, steps described in section 8.1 do not appear valid in this document anymore for Debian, because there is no such location on Debian:
sudo chmod 666 /opt/bitnami/apps/wordpress/htdocs/wp-config.php
AND because it seems an .htaccess does not exist either.
sudo chmod 666 /opt/bitnami/apps/wordpress/conf/htaccess.conf
Are there additional steps now which I've missed to be able to copy the necessary files for SSL to work properly on this new subdomain server now running Debian?
I was going to go through a new certificate request in the development server but wouldn't that invalidate the certificate currently installed for the primary domain?
In other words, how to properly copy the SSL files from the main Ubuntu server and configure the Debian subdomain server so that both wordpress installations have SSL correctly installed?
Thank you #mikemoy indeed, one can issue multiple wildcard certificates from different servers in a subdomain. Just went ahead and issued a new certificate.
I have a server with centos 6.7 64bit os , nginx web server (php-fpm55) and DirectAdmin control panel (custombuild 2).
I want all domains hosted on server access to phpmyadmin.
Now phpmyadmin with IP opens, But with domain not opens
For example:
domain.com/phpmyadmin : 404 not found
Please help me about this.
Thank you...
Which phpmyadmin version is installed on your server? Please check it at /var/www/html/ directory and try to create correct symlink to phpmyadmin directory.
ln -s /var/www/html/phpMyAdmin-version /var/www/html/phpmyadmin
I can't seem to get the smart host in Mamp Pro to work with OSX Yosemite (with Postfix 2.1 preinstalled). After configuring MAMP with my mail server details in looks like Mamp is using old or unsupported settings in Postfix.
If I restore the original configuration and stop MAMP, running Postfix manually from terminal results in Postfix starting without any issues. If I start up MAMP and configure to my mail server settings and apply them, if I stop Mamp and then try to start postfix from terminal it fails to start and reports unused parameter: mydomain_fallback=localhost, and fails to start.
If I edit the main.cf file for postfix and rem that line out, save main.cf and attempt to start postfix it tries to start and fails once again.
Does anyone know how to fix this?
Find main.cf, and change.
file:
/Applications/MAMP PRO/MAMP PRO.app/Contents/Resources
from:
mydomain_fallback = localhost
to:
#mydomain_fallback = localhost
inet_protocols=ipv4
stop/start MAMP
I have downloaded the newest MAMP version (3.0.5) and I am unable to connect to the localhost. All I get in Google is "Oops! Google Chrome could not find localhost:8888". I have tried all these things...
Re-downloaded MAMP several times and restarted comp
Changed the ports to 80 & 3306
Turned Firewall on and off and added "MAMP" as an incoming connection
Turned Web Sharing on and off
Checked and unchecked options in MAMP Preferences and hit ok/restart
Is there any solutions out there that have worked for you? I know it all varies, but anything to get this going would be a miracle at this point.
Thank you!
I was also experiencing the same issue on my OS X 10.9.4 with MAMP Pro 3.0.5 installed. The fix was very easy: missing info in my hosts file.
Solution found on: http://forum.mamp.info/viewtopic.php?f=2&t=82253
Note - I am using Mountain Lion
1) check your host file
go to folder /etc/
File path is: Your-hard-drive:private:etc:hosts
this is an invisible folder so you will need something that allows you to view invisible files folders on your Mac. I have Pathfinder installed which allows me to do this.
there should be an entry that makes localhost work
For me there was nothing in the hosts file. It was blank
2) Drag it to the desktop, that'll copy it
3) Paste the following into it and save it:
##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting. Do not change this entry.
##
127.0.0.1 localhost
255.255.255.255 broadcasthost
::1 localhost
fe80::1%lo0 localhost
4) Then delete the one in the etc folder (it'll ask for your password)
5) Then move the copy into the etc folder (password again)
6) Then open terminal and paste this in:
sudo killall -HUP mDNSResponder
(It will require your password)
7) I needed to restart my computer and then MAMP started working again!
MampGuy