MultiSite import

What issue or error are you experiencing?

I am using WP Migrate to export my Bedrock/Sage Wordpress site. When I import the site into Local, it is not recognized as a Multisite. Is there a way for me to fix this?


What steps can be taken to replicate the issue? Feel free to include screenshots, videos, etc

Export app via WP Migrate, import to local. Multisite is automatically set to ‘no’


System Details

  • Local Version:

  • Operating System (OS) and OS version: Windows 10


Local Logs

Attach your Local Logs here (Help Doc - Retrieving Local’s Log)


Security Reminder
Local does a pretty good job of scrubbing private info from the logs and the errors it produces, however there’s always the possibility that something private can come through. Because these are public forums, always review the screenshots you are sharing to make sure there isn’t private info like passwords being displayed.

Hi @Carter-Standish

Multisites can’t be directly imported and require a bit more setup. We have a document to walk you through here:

Thank you for the resource. I created a multisite in Local and replaced the files with my bedrock project. Unfortunately, I am getting this error with no guidance as to what could be causing it. Any ideas?

This is the log from Local Router’s Logs:

2023/11/14 22:26:50 [error] 22720#20384: *8 connect() failed (10061: No connection could be made because the target machine actively refused it) while connecting to upstream, client: ::1, server: mysite.test, request: “GET /wp-admin/ HTTP/1.1”, upstream: “http://xxx.x.x.x:xxxxx/wp-admin/”, host: “mysite.test”

Are you running other developer applications simultaneously? That could also cause similar issues. Apps like MAMP, XAMPP, or Docker for example.

Do you have any antivirus, security, or firewall applications that could be blocking Local? It looks like from the log it might be having trouble connecting.

I had MAMP and XAMPP installed as we were testing those as solutions. We’d like to stick with Local if we can get it working properly. I uninstalled both MAMP and XAMPP and I’m still getting the same issue.

We’re thinking about just connecting our local dev environment to our AWS cloud database instead. When I updated the DB_HOST, DB_NAME, DB_USER, and DB_PASSWORD in the .env file within our bedrock project, we are getting these messages:


This seems to be an issue related to the way Bedrock sets up its files as app/public/wp-config.php doesn’t exist. All of these are defined in our .env file. Is there a way to configure Local to look at the .env file instead?

Thank you for all of your help so far! We love Local and would really like to stick with it for our enterprise wide solution.

To keep you updated, the Adminer issue has been fixed. We are still looking to use a cloud database for local development though.

Hello,

We are continuing to have issues setting up or Local site. To just get it up and running, we are using the database that installs when creating a new site. We are hoping this will be enough to at least get something up in the meantime.

I updated .env and site.conf.hbs:

.env:
DB_NAME=‘local’
DB_USER=‘root’
DB_PASSWORD=‘root’
WP_ENV=‘development’
WP_DOMAIN=‘oursite.test’

site.conf.hbs:
root “C:\Users\me\Local Sites\localsite-test\app\local-wordpress\web\app”;

nginx error log:
2023/11/15 23:33:27 [error] 19520#10044: *2 directory index of “C:\Users\me\Local Sites\localsite-test\app\local-wordpress\web\app/” is forbidden, client: 127.0.0.1, server: , request: “GET / HTTP/1.0”, host: “local-test.local”

When opening the site, I get a 403 Forbidden error and when opening Admin, I get a 404 not found error. Any idea how we can resolve this issue?

Hi @Carter-Standish

Thank you for your patience and communication here. Can you share your Local Log with us for further investigation? There are some different ways to access and share Local Logs. For us to be able to troubleshoot thoroughly, please click the Download Local Logs button from the Support tab in Local. This will generate a zip archive that contains the Local log along with some other diagnostic information to help quickly zero in on any issues that Local is encountering.

Hello, this is the error file in its entirety. Let me know if there is anything else that I can provide.

2023/11/14 12:36:22 [error] 14176#27336: *24 connect() failed (10061: No connection could be made because the target machine actively refused it) while connecting to upstream, client: ::1, server: movementsite.local, request: "GET / HTTP/2.0", upstream: "http://127.0.0.1:10005/", host: "movementsite.local"
2023/11/14 16:29:26 [emerg] 31920#27280: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2023/11/14 16:29:26 [emerg] 24316#4672: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2023/11/14 16:29:27 [emerg] 31348#28544: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2023/11/14 16:35:57 [emerg] 30192#20524: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2023/11/14 16:35:58 [emerg] 22076#3164: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2023/11/14 16:35:59 [emerg] 11292#12460: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2023/11/14 16:39:21 [emerg] 33120#1784: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2023/11/14 16:39:22 [emerg] 21652#1704: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2023/11/14 16:39:22 [emerg] 30624#11384: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2023/11/14 16:40:08 [emerg] 30124#27548: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2023/11/14 16:40:08 [emerg] 31876#31000: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2023/11/14 16:40:09 [emerg] 12232#31732: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2023/11/14 16:40:56 [emerg] 15636#16552: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2023/11/14 16:40:57 [emerg] 23900#14312: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2023/11/14 16:40:57 [emerg] 25052#25700: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2023/11/14 16:41:16 [emerg] 29284#2352: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2023/11/14 16:41:16 [emerg] 20628#24160: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2023/11/14 16:41:17 [emerg] 22880#4632: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2023/11/14 16:41:18 [emerg] 13712#10712: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2023/11/14 16:41:18 [emerg] 1852#19880: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2023/11/14 16:41:19 [emerg] 20116#26328: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2023/11/14 16:42:55 [emerg] 23544#26516: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2023/11/14 16:42:56 [emerg] 23128#30312: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2023/11/14 16:42:56 [emerg] 19080#31732: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2023/11/14 16:43:02 [emerg] 5260#6008: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2023/11/14 16:43:03 [emerg] 7776#25500: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2023/11/14 16:43:03 [emerg] 28760#30660: bind() to 0.0.0.0:80 failed (10013: An attempt was made to access a socket in a way forbidden by its access permissions)
2023/11/14 17:48:34 [error] 16828#17824: *1 connect() failed (10061: No connection could be made because the target machine actively refused it) while connecting to upstream, client: ::1, server: movement2.local, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:10011/", host: "movement2.local"
2023/11/14 17:48:37 [error] 16828#17824: *2 connect() failed (10061: No connection could be made because the target machine actively refused it) while connecting to upstream, client: ::1, server: movement2.local, request: "GET /favicon.ico HTTP/1.1", upstream: "http://127.0.0.1:10011/favicon.ico", host: "movement2.local", referrer: "http://movement2.local/"
2023/11/14 17:49:51 [error] 17272#1892: *1 connect() failed (10061: No connection could be made because the target machine actively refused it) while connecting to upstream, client: ::1, server: movement.test, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:10011/", host: "movement.test"
2023/11/14 17:49:53 [error] 17272#1892: *1 connect() failed (10061: No connection could be made because the target machine actively refused it) while connecting to upstream, client: ::1, server: movement.test, request: "GET /favicon.ico HTTP/1.1", upstream: "http://127.0.0.1:10011/favicon.ico", host: "movement.test", referrer: "http://movement.test/"
2023/11/14 22:20:35 [error] 4188#9900: *1 connect() failed (10061: No connection could be made because the target machine actively refused it) while connecting to upstream, client: ::1, server: movement.test, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:10011/", host: "movement.test"
2023/11/14 22:20:37 [error] 4188#9900: *2 connect() failed (10061: No connection could be made because the target machine actively refused it) while connecting to upstream, client: ::1, server: movement.test, request: "GET /favicon.ico HTTP/1.1", upstream: "http://127.0.0.1:10011/favicon.ico", host: "movement.test", referrer: "http://movement.test/"
2023/11/14 22:22:13 [error] 22720#20384: *1 connect() failed (10061: No connection could be made because the target machine actively refused it) while connecting to upstream, client: ::1, server: movement.test, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:10011/", host: "movement.test"
2023/11/14 22:22:16 [error] 22720#20384: *1 connect() failed (10061: No connection could be made because the target machine actively refused it) while connecting to upstream, client: ::1, server: movement.test, request: "GET /favicon.ico HTTP/1.1", upstream: "http://127.0.0.1:10011/favicon.ico", host: "movement.test", referrer: "http://movement.test/"
2023/11/14 22:22:36 [error] 22720#20384: *2 connect() failed (10061: No connection could be made because the target machine actively refused it) while connecting to upstream, client: ::1, server: movement.test, request: "GET /wp-admin/ HTTP/1.1", upstream: "http://127.0.0.1:10011/wp-admin/", host: "movement.test"
2023/11/14 22:26:50 [error] 22720#20384: *8 connect() failed (10061: No connection could be made because the target machine actively refused it) while connecting to upstream, client: ::1, server: movement.test, request: "GET /wp-admin/ HTTP/1.1", upstream: "http://127.0.0.1:10011/wp-admin/", host: "movement.test"
2023/11/14 22:49:16 [error] 1236#23008: *1 connect() failed (10061: No connection could be made because the target machine actively refused it) while connecting to upstream, client: ::1, server: movement.test, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:10011/", host: "movement.test"
2023/11/14 22:49:18 [error] 1236#23008: *1 connect() failed (10061: No connection could be made because the target machine actively refused it) while connecting to upstream, client: ::1, server: movement.test, request: "GET /favicon.ico HTTP/1.1", upstream: "http://127.0.0.1:10011/favicon.ico", host: "movement.test", referrer: "http://movement.test/"
2023/11/14 22:54:21 [error] 16852#18876: *1 connect() failed (10061: No connection could be made because the target machine actively refused it) while connecting to upstream, client: ::1, server: movement.test, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:10011/", host: "movement.test"
2023/11/14 22:54:23 [error] 16852#18876: *1 connect() failed (10061: No connection could be made because the target machine actively refused it) while connecting to upstream, client: ::1, server: movement.test, request: "GET /favicon.ico HTTP/1.1", upstream: "http://127.0.0.1:10011/favicon.ico", host: "movement.test", referrer: "http://movement.test/"
2023/11/14 22:55:11 [error] 16852#18876: *2 connect() failed (10061: No connection could be made because the target machine actively refused it) while connecting to upstream, client: ::1, server: movement.test, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:10011/", host: "movement.test"
2023/11/14 22:55:13 [error] 16852#18876: *2 connect() failed (10061: No connection could be made because the target machine actively refused it) while connecting to upstream, client: ::1, server: movement.test, request: "GET /favicon.ico HTTP/1.1", upstream: "http://127.0.0.1:10011/favicon.ico", host: "movement.test", referrer: "http://movement.test/"
2023/11/14 22:55:25 [error] 26544#20188: *1 connect() failed (10061: No connection could be made because the target machine actively refused it) while connecting to upstream, client: ::1, server: movement.test, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:10011/", host: "movement.test"
2023/11/14 22:55:27 [error] 26544#20188: *1 connect() failed (10061: No connection could be made because the target machine actively refused it) while connecting to upstream, client: ::1, server: movement.test, request: "GET /favicon.ico HTTP/1.1", upstream: "http://127.0.0.1:10011/favicon.ico", host: "movement.test", referrer: "http://movement.test/"
2023/11/14 22:55:32 [error] 26544#20188: *1 connect() failed (10061: No connection could be made because the target machine actively refused it) while connecting to upstream, client: ::1, server: movement.test, request: "GET /wp-admin/ HTTP/1.1", upstream: "http://127.0.0.1:10011/wp-admin/", host: "movement.test"
2023/11/14 23:01:17 [error] 14956#13260: *3 connect() failed (10061: No connection could be made because the target machine actively refused it) while connecting to upstream, client: ::1, server: movementgyms.test, request: "GET / HTTP/2.0", upstream: "http://127.0.0.1:10011/", host: "movementgyms.test"
2023/11/14 23:11:41 [error] 20120#8544: *3 connect() failed (10061: No connection could be made because the target machine actively refused it) while connecting to upstream, client: ::1, server: movementgyms.test, request: "GET / HTTP/2.0", upstream: "http://127.0.0.1:10011/", host: "movementgyms.test"
2023/11/15 09:08:11 [error] 11196#18256: *1 connect() failed (10061: No connection could be made because the target machine actively refused it) while connecting to upstream, client: ::1, server: movementgyms.test, request: "GET /favicon.ico HTTP/2.0", upstream: "http://127.0.0.1:10011/favicon.ico", host: "movementgyms.test", referrer: "https://movementgyms.test/"
2023/11/15 11:17:42 [error] 25232#4960: *3 connect() failed (10061: No connection could be made because the target machine actively refused it) while connecting to upstream, client: ::1, server: movementgyms.test, request: "GET / HTTP/2.0", upstream: "http://127.0.0.1:10011/", host: "movementgyms.test"
2023/11/15 11:17:44 [error] 25232#4960: *3 connect() failed (10061: No connection could be made because the target machine actively refused it) while connecting to upstream, client: ::1, server: movementgyms.test, request: "GET /favicon.ico HTTP/2.0", upstream: "http://127.0.0.1:10011/favicon.ico", host: "movementgyms.test", referrer: "https://movementgyms.test/"
2023/11/15 11:19:07 [error] 25232#4960: *3 connect() failed (10061: No connection could be made because the target machine actively refused it) while connecting to upstream, client: ::1, server: movementgyms.test, request: "GET / HTTP/2.0", upstream: "http://127.0.0.1:10011/", host: "movementgyms.test"
2023/11/15 11:30:38 [error] 25232#4960: *10 connect() failed (10061: No connection could be made because the target machine actively refused it) while connecting to upstream, client: ::1, server: movementgyms.test, request: "GET /favicon.ico HTTP/2.0", upstream: "http://127.0.0.1:10011/favicon.ico", host: "movementgyms.test", referrer: "https://movementgyms.test/"
2023/11/15 11:39:22 [error] 4324#18152: *3 connect() failed (10061: No connection could be made because the target machine actively refused it) while connecting to upstream, client: ::1, server: movementgyms.test, request: "GET / HTTP/2.0", upstream: "http://127.0.0.1:10011/", host: "movementgyms.test"
2023/11/15 11:39:25 [error] 4324#18152: *3 connect() failed (10061: No connection could be made because the target machine actively refused it) while connecting to upstream, client: ::1, server: movementgyms.test, request: "GET /favicon.ico HTTP/2.0", upstream: "http://127.0.0.1:10011/favicon.ico", host: "movementgyms.test", referrer: "https://movementgyms.test/"
2023/11/15 13:06:34 [error] 3224#5468: *160 connect() failed (10061: No connection could be made because the target machine actively refused it) while connecting to upstream, client: ::1, server: movement.test, request: "POST /wp-admin/admin-ajax.php HTTP/1.1", upstream: "http://127.0.0.1:10004/wp-admin/admin-ajax.php", host: "movement.test", referrer: "http://movement.test/wp-admin/themes.php"
2023/11/15 22:47:31 [error] 29392#11196: *1 connect() failed (10061: No connection could be made because the target machine actively refused it) while connecting to upstream, client: ::1, server: movement-test.local, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:10010/", host: "movement-test.local"
2023/11/15 23:05:03 [error] 26816#24520: *1 connect() failed (10061: No connection could be made because the target machine actively refused it) while connecting to upstream, client: ::1, server: movement-test.local, request: "GET /wp-admin/ HTTP/1.1", upstream: "http://127.0.0.1:10010/wp-admin/", host: "movement-test.local"
2023/11/15 23:05:35 [error] 23896#6152: *1 connect() failed (10061: No connection could be made because the target machine actively refused it) while connecting to upstream, client: ::1, server: movement-test.local, request: "GET /wp-admin/ HTTP/1.1", upstream: "http://127.0.0.1:10010/wp-admin/", host: "movement-test.local"

Hello,

Looking to see if there are any updates on the occurring errors or how we can get support. @Nick-B

Thanks

The errors in the log look like Port Conflicts. Sometimes changing your Router Mode will get around these but Localhost won’t work for multisites. You can try to see if there is anything conflicting with Local by trying the steps here:

  • (If using Mac) Run the command lsof -nP -iTCP -sTCP:LISTEN

  • (If using Windows) Run the command netstat -ano

Once you run that command you should see a list of listening ports. If you see a particular program making use of those ports, you can then kill that process by running sudo kill -9 XXX where XXX is the PID number of that process. (On Windows you will use taskkill /F /pid XXX where XXX is the PID number of that process)

There are also some more details around this and other troubleshooting steps at this link if needed: Stopping Whatever Is Listening On Port 80.

Hello,

We restarted from scratch and got the database connected properly and we are clear from nginx/php errors. Now we are getting a blank screen when opening the site and this error when trying to connect to admin:

Any ideas for a solution?

Hi @Carter-Standish

Are you still running into this error?

If you create a new, blank site in Local are you able to access that okay?

If found this thread which might be helpful:

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.