Syncing MAMP MySQL Database on MEGA - mysql

SO I've read countless tutorials and I've spent hours trying to solve this but have run out of ideas. Trying to sync my Wordpress database on MEGA (every other tutorial said dropbox but I got MEGA) and everything but one things works on my windows PC.
I've installed MAMP for both (available for Mac and windows now), made them the same settings and properly integrated MEGASync with it. I created the symlink from both Windows and Mac and updates seem to be happening when I make changes or fool around with wp-config to fix this.
With wordpress I ran the installer on the MAC and it works fine for syncing. On Windows 8.1 however everything functions between MEGA but when connecting to http://localhost:8888 or http://127.0.0.1:8888 Im simply getting a 'Waiting for Connection". Opening phpmyadmin from either computer shows the database I created as well.
Things I've tried.
- Turn off firewall
- Ran a netstat -a command and found it was listening on 0.0.0.0:8888
- Tried to visit localhost:8889 (mysql) and it downloaded a file.
- Made sure my hosts file had 127.0.0.1 localhost and has ::1 localhost
- Can ping localhost and 127.0.0.1
- Checked apache logs and found them empty
Anything I can do to try and log where to narrow down why it's timing out (it seems) on my local windows box?

Not sure if it's much of a solution but did solve this. I uninstalled both MAMP servers (Mac and Windows) and did the entire setup process but started on the Windows machine first this time.
I think the problem was a different structure had been synced (not synced) from both computers (Mac was looking like a different file structure).
No I see the proper contents in both directories.

Related

Can't log in to an app running on LocalHost - no network activity?

I'm working on an app with a team. They are able to log in fine when running it on their local servers, however when I try to do so I get 'Invalide username / password' and no network activity or console errors in dev tools.
I have no idea why this could be, we're working on the exact same code - clearly it's something on my machine.
Has anyone come across anything like this before?
(Have tried other browsers and still nothing).
Maybe you need to check your server instalation on your machine.
For example, if you are using XAMPP to manage your Apache maybe there is some configuration that was set in the wrong way.
My advice is, save your code and re-install your server, pay attention to all configuration details and see if the problem is solved.

Did El Capitan DP8 Break Connections to LocalHost in MAMP PRO 3.4?

Here's the situation. This morning after installing El Capitan DP8, I noticed that I was no longer able to connect to my WordPress blog. Firefox's status bar just says connecting, but it never connects. As a first recourse, I manually reinstalled WP 4.3, and set overall folder/file permissions in my WP directory to 777 as a test. Reinstallation and permissions change didn't help.
However, then I discovered that neither could I connect to any of the domains which I host with MAMP PRO. So my next step was to reinstall MAMP PRO 3.4, replacing the db and htdocs folders with my original ones. Still no success.
Mind you, I have no problem connecting to external websites via Firefox. It is just my local domains that don't work. Firefox just says "connecting", followed by the intended URL.
In addition, I have done the following, although not necessarily in this order:
Installed OS X El Capitan DP8 Firmware Update.
Installed OS X El Capitan DP8 a second time.
Verified that my "hosts" file is in order and not corrupted via nano.
Used "Sequel Pro" to check, and if necessary, repair all of the tables in my WordPress database. None required repair, and I can see all of the data in the tables going back four years.
Restarted my cable modem and Apple Airport Extreme.
Verified my LAN settings via Airport Utility.
Verified that the folder paths to my various domains are still correct in MAMP PRO.
Despite doing all of the above -- which included a few machine restarts -- I am still unable to connect to my local domains.
MAMP PRO starts up just fine, and all of my settings in MAMP PRO look fine. My ports are set to the default 80, 443 and 3306, as they have always been. I see all of my domains listed on the "Hosts" tab. My Apache and mySQL users are set to the suggested ones.
At this point, I am at a loss regarding what to do. Has anyone else encountered this? Do you have any possible solutions?
Thanks in advance.
Just came across this and had the exact my.cnf and renamed the latest version to something like my-old.cnf, restarted MAMP Pro and it worked.
Hope that helps others.

Xampp doesn't work on Mac X

So here is what happens when i run xampp by clicking on the manager-osx.
I click on "manager-osx".
Icon jumps in the dock as if it is starting the service.
Asks for admin password. I enter the password.
It accepts the password, and application keep jumping in the docs for 3-4 times.
The app disappear from the dock.
The issue started after i have quit few processes from the activity monitor.
I am not sure what has affected xampp and can't remember what services i have stopped as there were many.
Solution applied so far:
Restarted my MacBook Pro.
Exit all other application and tried to run xampp.
Made sure no other application is running on port 80.
Removed xampp from applications and tried to reinstalled. Same issue with re-installation process, It asks for admin password and then nothing happens.
search online for any help but nothing helpful found.
I haven't got any experience with XAMMP but MAMP works always fine for me. MAMP has everything I need in terms of functionality.
I would recommend MAMP
If MAMP is not the best solution for you. You can install manualy
APACHE + PHP + MYSQL (It's not so hard)
Just go step by step using tutorial like
This
Manual installation will give you much more controll on your enviroment.
And also you will have better output to attach it here if you can't find a problems.
Of course it's little bit longer than 3 clicks. But on all production servers you need to install environment manually. This knowledge you will use later much more times. You will better understand how all is works and how to find reason of bug.(error)

MAMP not connecting to localhost

Just updated MAMP to version 3.2.1 on Yosemite. Both Apache and MySQL servers are green but when I go to my localhost I keep getting: This webpage is not available ERR_NAME_NOT_RESOLVED in browser (Chrome). I’ve tried incognito browsing and Firefox with the same result, tried both the MAMP default port settings and ports 80 & 3306, tried a reinstall of MAMP and rolling back to previous install of MAMP; all without success.
Can anyone suggest how to fix this…it’s starting to drive me crazy!
Possible Thoughts;
In your /Applications/MAMP/htdocs/ folder, is there something in there for your browser to load? Some sort of index.html or index.php file? Could it have gotten removed accidentally?
When you launch MAMP and go to Preferences -> Ports, what is the Apache port? You mentioned you tried the default (8888/8889) and 80/3306, but could the port number somehow have gotten changed?
Is there any chance that some other Apache service is running? This is unlikely as you mentioned that MAMP shows Apache status as green, but it could be worth stopping MAMP, opening Terminal and doing sudo apachectl stop, returning to MAMP and changing the ports to 80/3306, then returning to Terminal and doing sudo apachectl restart. Then return to MAMP and start services again.
If none of the above work, what if you set the Apache port in MAMP's preferences to something random, like 8712, and then try http://localhost:8712/ to see if it loads.
Let us know if you've tried those already!
Had a similar issue. If 127.0.0.1 is working then you just need to point localhost to 127.0.0.1. Edit /etc/hosts file (requires sudo) and include
127.0.0.1 localhost
That resolved it for me.
This still happens occasionally when updating macOS.
Going through all local Wordpress sites and changing the dev url isn't ideal, though necessary when changing the port.
What rather solved the issue for me was restarting Apache as suggested by #ZbadhabitZ, keeping original port number:
sudo apachectl restart
I had this issue because I had Docker Desktop running at the same time; I shut this down and it started working so it must have been a port conflict.

problems running xamp

I am using a open source document repositary kordil edbms which works fine in my windows 7 machine .
But when i installed it in windows small business server, xamp is not running. when i start task manager httpd itself is not getting shown. I went to xamp control panel and it says error running mysql busy.I have share point in that machine which also has localhost 80.
So I changed the apache port.
I changed the apache port in httpd.conf file in 2 places
listen
server name
It seems i need to change the port for mysql also. Now what is the option to change the port for xamp mysql or am i going wrong some where else. Please also look at the screenshot of xamp control panel.
Quit Skype and then restart all services from your XAMPP and let me know if its work or not.
Port conflict as Skype also consumes 80 by default
Click on SCM and manage services by starting and stopping.
EDIT
check this link for both to work with - http://www.binodranabhat.com.np/blog/using-xampp-and-iis-together/
MYSQL not working because xampp which path excepting that path not getting automatically .
that is reason behind xampp mysql not start
go to window +R press then open cmd with run as administration then type this command
sc delete mysql
then after start mysql problem resolved.
Fixing Apache Port Conflicts
Another error message that is pretty common to see when working with XAMPP is a notification in the XAMPP control panel that the ports Apache needs to use, ports 443 and 80, are already being used by another application.
A message from the XAMPP control panel letting us know Skype is using ports 443 and 80
In the case of the error message in the image above, this is a pretty easy fix. The offending application is Skype. If you see the same message, close Skype completely and restart XAMPP to solve the problem. Skype is a frequent-flier on the port-blocking scene and pretty easy to identify and remediate. Unfortunately, things aren’t always so simple.