Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 4 days ago.
Improve this question
I would like to replicate my WordPress MySQL database as described in the MySQL documentation 5.7 - Replication.
I am attempting to configure an externally hosted instance of Wordpress to act as the Master to a Slave MySQL database hosted on a.n.other platform. Understandably the MySQL .ini file is not visible on the host system, and I am not sure that designating the server id or the Master/Slave status will be available either (if I am wrong about this I will be delighted). I am attempting a solution using WP Data Access, but they are currently locked out of Dropbox and have been for a few days so I am reluctant to commit a vital part of the architecture to them just yet.
Another option has occurred to me - can anyone out there tell me why it wont work (or suggest another solution).
If I were to set up a locally hosted instance of WordPress and configure it to act as Master, and then ported the whole thing to the external host, would the .ini settings etc survive the journey? It may be that these questions are better directed to the host, but their position is that they host WordPress (exclusively) but do not offer any sort of MySQL support.
Have attempted to again access to the .ini file within WordPress's database, with no success.
Have upgraded WP Data Access to Premium, but need a Premium Data Service to connect the host with the other platform and am waiting for the host to get back to me.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
This image shows the error pop up when I try to test the connection
Current Set Up: 2015 MacBook Pro. OS 10.15.7
Things that I have tried:
System preferences > MySQL > initialize setup.
Checked Username is correct on AWS RDS set up.
Checked the endpoint address.
Tested connection on a 127.0.0.0 database. Works fine.
Sounds like you have not configured the Security Group related to your RDS instance. You must set up inbound rules for the security group to connect to the database. You can set up one inbound rule for your development environment and another for Elastic Beanstalk (assuming you use that to host your app). Setting up an inbound rule essentially means enabling an IP address to use the database. Once you set up the inbound rules, you can connect to the database from a client such as MySQL Workbench. For information about setting up security group inbound rules, see Controlling Access with Security Groups.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
Can someone give me a clear explanation of the differences between mysql (command line tool), mysqladmin (client tool for performing administrative tasks) and mysqld (mysql server).
You could easily find that out yourself by just reading the man pages about the three commands:
mysqld is the server executable (one of them)
mysql is the command line client
mysqladmin is a maintainance or administrative utility
They serve different purposes. There is not simply a "difference" between them. For different task you have different utilities. Just like you use a screwdriver for a screw and a hammer for a nail.
If you want to query a database server you need to connect to it using a client. The client connects to the server which serves the mysql service. If you need to do administrative adjustments in the server you need an administration utility.
Typically the server is started and stopped by the operating system it runs on, so at bootup and shutdown times. The clients (there are different types of clients) are started and used by users or programs handling with data inside the server. And the administrative staff uses the administrative tool to administer the servers on their systems.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I tried installing ejabberd on my linux 12.04 machine but I am a bit confused as to what goes into the ejabberd server domain field. I put in localhost but when I start, it opens an error page. I installed using a binary file I downloaded from the process one website. Anybody knows what exactly should go into that field? Thank You.
Think of the domain name as the name that will serve you. For example, if you create a xmpp server for domain users inside your company example.com, the domain is example.com, since accounts with which users will be connected user1#example.com, user2 # example . com, etc. ..
A single server can serve different domains ejabberd.
As discussed ppolv, usually coincides with the name of your domain in your network, you can configure as well, for example, the DNS server SRV records required for the XMPP protocol.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 12 months ago.
Improve this question
I'm renting a VPS and right now it is being used as my web server and MySQL database. When renting a VPS, they give you SSH access to it. Is there a way for me to hide (make it seem like it doesn't exists) SSH and MySQL outside connections except for my own?
I don't want public users to see that SSH is enabled even though they probably won't guess the password.
You can use Port knocking to hide SSH. I would close down the mysql port and use a SSH tunnel for this.
Install a port-knock daemon. It looks for "special "knock" sequences of port-hits" and then opens the firewall like you want it.
knock myserver.example.com 123:tcp 456:udp 789:tcp
mysql: you could maybe forbid connections except from localhost, and use ssh port forwarding to remotely access your database
ssh: use a non-standard port and switch to public key authentication. You will have to leave a port open anyway.
Fail2ban may be worth trying. It will block connections to your machine from a given address after repeated failures.
If you're accessing the server from only one address (or very few addresses), you can add a firewall rule to block any access from anything other than those addresses. However, if you're going to be accessing the site from (say) your cellphone, you can't do this, as your cell is highly likely to be behing a NAT firewall and you can't predict what the external IP would be.
You can also move SSH onto something other than the default port 22 to block the "stupid" ssh attack scanners, though that won't stop dedicated port scanners.
Some thoughts...
You could run sshd on a non-standard port. Port-scanners will be able to notice it, but the scripts that just bang on port 22 won't see it.
You could configure it to only allow connections from specified hosts (better to do this at the firewall level, come to think of it). This would limit your ability to log onto it from anywhere but would allow sshd to immediately reject connections from any place other than the specified hosts.
I think the best two options are:
Hide the servers behind a firewall and use a VPN to communicate.
Change the port numbers to something random so they won't be detected by a default port scan.
Today we rely more on browser based sessions as they tend to be more secure thanks to modern browsers' sandboxing and generally higher security level, freely available auto-renewable SSL certificates, and well understood MFA systems.
Web based SSH terminals are common, and they can be protected by federated authentication (OAUTH/SAML/OIDC) identity providers (also available for free! Auth0, DUO, but also Google, Github, etc) and easily complemented with multi factor authentication.
A good implementation of this concept comes for free if you have a Linode VPS: it's called the LISH (Linode Shell). Provided both as text based (Weblish) and canvas based (Glish).
If you are not on Linode, you can host your own Apache Guacamole which is equally great. And of course, it comes with SAML, OIDC, TOTP MFA, etc.