Creating a local WordPress site is a routine for most developers, though sharing a live preview with clients or multiperson collaboration in real-time without having to waste time on complicated networks and open ports is always a big problem. That’s where Pinggy comes into play – a simple and lightweight tool for sharing local WordPress sites, that works in harmony with LocalWP by Flywheel tool, helps to tunnel your site in order not to trouble yourself with its remote accessibility. This tutorial will help you to find out how you can make the most of Pinggy if you have a local WordPress environment set up.
Configure Pinggy Pro:
mysite.a.pinggy.link
.Run Command: Open terminal and run:
ssh -p 443 -L4300:localhost:4300 -o StrictHostKeyChecking=no -o ServerAliveInterval=30 -t -R0:your-subdomain.a.pinggy.link:80 <your-token>@a.pinggy.io
Access Site: Use the generated Pinggy URL to access your local WordPress site remotely.
Pinggy allows you to connect to Local sites from outside your network without the need for a VPN, or even to change firewalls. It’s especially useful for developers working with LocalWP by Flywheel, what helps to solve usual issues like reverse proxying, secure connections or mixed content. Pinggy in one way or another provides its users with the means to remotely access local WordPress setups, and as such, is an essential tool for developers to create and test their sites.
To get started with Pinggy for Creating a LocalWP site sharing, you’ll need the following:
With these tools, developers can easily get started, using Pinggy’s tunneling power to share their local site with clients, gather feedback, showcase to friends, host hobby projects, and more
Pinggy allows the user to securely share out the LocalWP setup allowing them to access and manage their WordPress site from any location. Below is the procedure on configuring Pinggy for LocalWP with screenshot being included for clarity.
if you have recently purchased a Pinggy Pro subscription, please enter the Pinggy dashboard. Go to Subdomain settings – it is located at the bottom of the left menu – then click Edit under the ‘Subdomain’ heading and enter the subdomain you wish to use.
Secondly, using LocalWP go to the Site Domain section and paste the subdomain obtained from Pinggy.
Open LocalWP by Flywheel and select your WordPress site. Click the “open Site” button to launch the site Locally.
In the terminal, use the updated Pinggy command, which now includes a token from your Subdomain setup. Replace moksh.a.pinggy.link
with your chosen subdomain.
ssh -p 443 -t -R0:moksh.a.pinggy.link:80 jYEfZnpL3zR@a.pinggy.io u:Host:moksh.a.pinggy.link x:reverseproxy:moksh.a.pinggy.link
Customize your command:
This command establishes a secure SSL connection from your local server to Pinggy’s server, making the site available for remote access.
moksh.a.pinggy.link
) on port 80, allowing the LocalWP site to be accessed through this subdomain.Once the Pinggy tunnel is live, you can access your LocalWP site from anywhere using the URL generated by Pinggy.
https://moksh..pinggy.link
).By following these steps, you can efficiently set up and manage remote access for your LocalWP WordPress site using Pinggy.
As with any tool, there may be occasional issues when using Pinggy with LocalWP. Here are some common problems and solutions.
If your site is hosted over HTTPS, but some of the resources that are being called, for instance images or scripts are in HTTP, then you may get mixed content messages. This can distort order of loading of assets and affects the look and feel of the site.
It is mainly attributed to improper headers or wrong site locations.
u:Host:testping.local
) and verify that this value is the same as your local site address.LocalWP usually sets the site to run on port 80 and sometimes this may result to conflicts.
Following these instructions as well as tips on troubleshooting you can successfully configure and use Pinggy for providing remote access to your LocalWP WordPress site.
Here are some additional recommendations to prevent issues when working with Pinggy and LocalWP:
Note that you may experience connectivity problems In that cas you append `ServerAliveInterval=10’ at the Pinggy command-Function:. It sends a “heartbeat” every 10 seconds to keep the session alive and useful for avoiding timeout issues while working through long sessions during development.
Pinggy makes LocalWP site share as easy as possible and gives developers the chance to get real feedback, discuss and test.