Local Community

Ubuntu Instance Fails Create New and from Cloud Backup

Issue Summary

Local running on Ubuntu in Win 11 WSL. New site from Cloud Back fail, also new site creation not working. Reason for all this is my Windows Local also stopped working. Maybe Notes addon, I dunno.

Troubleshooting Questions

  • Does this happen for all sites in Local, or just one in particular?
    yes

  • Are you able to create a new, plain WordPress site in Local and access it in a Browser?
    no

Replication

Describe the steps that others can take to replicate this issue. If you have screenshots that can help clarify what is happening, please include them!

System Details

  • Which version of Local is being used?

  • What Operating System (OS) and OS version is being used?

    • For example: macOS Catalina or Windows 10 Professional
  • Attach the Local Log. See this Help Doc for instructions on how to do so:

    • local-logs.zip (666 Bytes)

      `(local:16638): libnotify-WARNING **: 04:12:57.775: Failed to connect to proxy
      3/17/2022, 4:12:57 AM [info] [main] HostsFileService: Updating hosts with
      3/17/2022, 4:12:57 AM [error] [main] SiteProcessManagerService: Unable to start site. – {“stack”:“Error: Error: User did not grant permission.\n\nError getting authority: Error initializing authority: Could not connect: No such file or directory\n\nexitCode: 127\n at %%appPath%%/main/_helpers/sudo.js:1:1098\n at %%appPath%%/node_modules/sudo-prompt/index.js:191:11\n at ChildProcess.exithandler (child_process.js:324:5)\n at ChildProcess.emit (events.js:315:20)\n at ChildProcess.EventEmitter.emit (domain.js:467:12)\n at maybeClose (internal/child_process.js:1048:16)\n at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5)”}
      3/17/2022, 4:13:46 AM [info] [main] Process: Killing process – {“process”:“mailhog”,“pid”:17331}
      3/17/2022, 4:13:46 AM [info] [main] Process: Killing process – {“process”:“phpFpm”,“pid”:17336}
      3/17/2022, 4:13:46 AM [info] [main] Process: Killing process – {“process”:“mysql”,“pid”:17337}
      3/17/2022, 4:13:46 AM [info] [main] Process: Killing process – {“process”:“httpd”,“pid”:17340}
      3/17/2022, 4:13:46 AM [error] [main] SiteProvisionerService: Unable to provision site. – {“stack”:“Error: Error: User did not grant permission.\n\nError getting authority: Error initializing authority: Could not connect: No such file or directory\n\nexitCode: 127\n at %%appPath%%/main/_helpers/sudo.js:1:1098\n at %%appPath%%/node_modules/sudo-prompt/index.js:191:11\n at ChildProcess.exithandler (child_process.js:324:5)\n at ChildProcess.emit (events.js:315:20)\n at ChildProcess.EventEmitter.emit (domain.js:467:12)\n at maybeClose (internal/child_process.js:1048:16)\n at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5)”}
      This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
      Error: Error: User did not grant permission.

Error getting authority: Error initializing authority: Could not connect: No such file or directory

exitCode: 127
at /opt/Local/resources/app.asar/main/_helpers/sudo.js:1:1098
at /opt/Local/resources/app.asar/node_modules/sudo-prompt/index.js:191:11
at ChildProcess.exithandler (child_process.js:324:5)
at ChildProcess.emit (events.js:315:20)
at ChildProcess.EventEmitter.emit (domain.js:467:12)
at maybeClose (internal/child_process.js:1048:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5)
3/17/2022, 4:13:55 AM [warn] [main] undefined: Unhandled Rejection. – {“reason”:{},“p”:{},“eventId”:“2f228bdf1a804959b36573ebe497dadc”}
3/17/2022, 4:13:55 AM [info] [main] DeleteSiteService: Deleting %%site.runData%%
3/17/2022, 4:13:55 AM [error] [main] HostsFileService: Could not update hosts. – {“error”:{},“stdout”:{},“stderr”:{},“exitCode”:{}}
gio: file:///home/groot/Local%20Sites/cgcolocalbackup: Error trashing file /home/groot/Local Sites/cgcolocalbackup: No such file or directory
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
Error: Failed to move item to trash
3/17/2022, 4:14:02 AM [warn] [main] undefined: Unhandled Rejection. – {“reason”:{},“p”:{},“eventId”:“6fa2d848c5a642fc935680d8baaeefd1”}

(local:16638): libnotify-WARNING **: 04:14:03.346: Failed to connect to proxy

(local:16638): libnotify-WARNING **: 04:14:03.346: Failed to connect to proxy

(local:16638): libnotify-WARNING **: 04:14:03.346: Failed to connect to proxy
3/17/2022, 4:14:03 AM [info] [main] HostsFileService: Updating hosts with
3/17/2022, 4:14:03 AM [error] [main] HostsFileService: Could not update hosts. – {“error”:{},“stdout”:{},“stderr”:{},“exitCode”:{}}
[13800:13800:0317/041528.632148:ERROR:web_app_url_loader.cc(136)] Error loading about:blank page took too long to load.
[13800:17473:0317/041532.678142:ERROR:get_updates_processor.cc(260)] PostClientToServerMessage() failed during GetUpdates with error 2`

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.

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