I have migrated to a new webhost that has MacOS Mojave installed. My previous installation used El Capitan (or maybe it was Yosemite) and worked perfectly. Previously, I had everything set up using Mac Server. However, as you may already know, over the last few OS "upgrades," Apple has reduced Server to the point that it now worse than useless. It no longer controls web hosting or anything else you might want to do. So I have been trying to use ApacheGUI. After mucking around in httpd.conf and httpd-vhosts.conf, my website is now responding on port 8080. Previously, my installation of Apache Tomcat used port 8080, but because I don't need Tomcat, this is really a non-issue. The problem is that the MacOS Server webpage ("Welcome to macOS Server") responds on port 80. I can't figure out how this is possible. I have copied my entire website to both /Library/WebServer/Documents (the document root specified in httpd.conf) and /Users/UserName/Website/website/com (the document root specified in httpd-vhosts.conf).
Any assistance would be appreciated. I have a working knowledge of how to get around in terminal and nano, but I don't know much about setting up a webserver manually thanks to my decade+ reliance on the now-deprecated MacOS Server.
Related
I have an old iMac running 10.7.5. I am trying to connect to my Ubuntu file server (running 22.4.1 LTS) to save a huge amount of data before discontinuing the iMac.
Every time I try smb://192.168.1.5, I get "There was an error ... please check the server name or IP address...".
Using the same method and IP address on my Mac mini using MacOS 13.1 gets me connected without issues.
I tried using "cifs://192.168.1.5", but got the same error.
I also tried going to System Settings to turn on File Sharing (although this is for sharing files that are ON the iMac) because I read that turning this off and on might fix this issue. This is not the case.
Since I am not well versed with older Mac systems, I am unsure on how to solve this. Any ideas would be welcome.
I had Docker Desktop installed for Mac Catalina last year, but I haven't used it until today, a day after updating to Monterey (from Big Sur) (I'm on a Mac Intel) when I downloaded the latest Docker Desktop dmg file (~500MB), which had me drag the icon to the folder, which I then chose to replace the existing .app file... but when opening the file (in /Applications), I get this new pop-up:
I've tried to search what this is actually going to do, and I can't tell; I use Cisco AnyConnect VPN sometimes for a project, and I'm afraid there'll be a conflict... but ultimately, I don't know what exactly I'm giving access to or if it's actually necessary. I just want to try Docker with Laravel Sail.
I know macOS over the last several years (since Catalina really) has changed filesystem stuff a lot and I end up going down StackOverflow rabbit holes trying to get things to work, so I'm hoping someone else knows how this works or has made it work and can advise.
I am a frontend developer and I have set up my projects to run on 192.XXX.X.X instead of localhost so I can access it from my phone.
Recently, this stopped working. On all projects.
Ones using webpack and ones using simple VSCode live-server.
Unfortunately I have issues troubleshooting because in the meantime I have installed a lot of things, so I am not sure what could be the culprit.
Most recent things I have done:
Installed parallels
Upgraded to Big Sur
Realized that company provided VPN doesn't work on it
Reverted back with TimeMachine to Catalina
Any suggestions are welcome.
Somehow the node.js server used for docpad running on my MacBook (running 10.8.4) are no longer accessible. Docpad (using the default "docpad run") normally publishes on port 9778, and is accessible via localhost:9778 (or 127.0.0.1:9778), and this used to work just fine, and was reliable. Now, however, Safari says 'Safari can't connect to the server "localhost"' ... same thing for Chrome, so it's not a Safari issue.
The one thing that HAS changed, is that now I have OS X Server 2.2 installed ... and the default server webpage does appear at "localhost" or "localhost:80".
Furthermore, another node.js server (the one available with punch), works just fine on any IP number I give it.
Just to make things even more confusing, the docpad server access started to work again last night after a clean install of the twitter-bootstrap skeleton, and then stopped again this AM. I restarted the MacBook ... no change. I turned the web server off using the OS X Server console ... no change.
Something weird with the docpad server code?
Any ideas?
I'm building a web app on my Mac and have so far been testing with XAMPP. I'm looking at finding a virtual server vendor to host my application but have found almost none that is compatible with Mac, Apache, PHP and MySql. I don't want to go the Mac Mini route for now.
Does anyone have any suggestions on how I could do this or what vendor to use?
If it's a PHP/mySQL app, chances are it's not very dependent on the OS it's running on. Unless you have something totally Mac specific running in your app, getting a normal Linux VPS may be the way to go.