![]() ![]() Testing conducted by Apple in September 2022 on production 13-inch MacBook Pro systems with Apple M2, 8GB of RAM, 256GB SSD, and prerelease macOS Ventura.Performance will vary based on usage, system configuration, network connection, and other factors. Tested with prerelease Safari 16.1 and Chrome v1.125. Tested on production 13-inch MacBook Pro systems with Apple M2, 8GB of RAM, 256GB SSD, and prerelease macOS Ventura. Testing conducted by Apple in September 2022 by measuring page load performance of snapshot versions of 10 popular websites under simulated network conditions.Performance will vary based on system configuration, network connection, and other factors. Tested with prerelease Safari 16.1 with WPA2 Wi-Fi network connection. Tested on 13-inch MacBook Pro systems with Apple M2, 8-core CPU, 10-core GPU, 8GB of RAM, and 256GB SSD, as well as a production 1.7GHz quad-core Intel Core i7-based 13-inch MacBook Pro system with Intel Iris Plus 645 graphics, 16GB of RAM, and 2TB SSD, all configured with prerelease macOS Ventura. Testing conducted by Apple in September 2022 using JetStream 2.1, MotionMark 1.2, and Speedometer 2.1 performance benchmarks.Devices tested with a WPA2 Wi-Fi network connection. Tested with prerelease Safari 16.1 and latest stable versions of Chrome, Microsoft Edge, and Firefox at the time of testing on: 13-inch MacBook Pro systems with Apple M2 and prerelease macOS Ventura, and Intel Core i7-based PC systems with Intel Iris Xe Graphics and Windows 11 Pro iPad Pro 12.9-inch (5th generation) units with prerelease iPadOS 16.1, and Intel Core i7-based PC systems with Intel Iris Xe Graphics and Windows 11 Pro and iPhone 13 Pro Max with prerelease iOS 16.1, and Qualcomm Snapdragon 8 Gen 1-based smartphones with Android 12. Then press Advanced and go to the Proxies tab. To ensure that the proxy is not interfering with connections to your local LiveReload server, go to System Preferences → Network and select your active network adapter (e.g. If you have an HTTP proxy configured, this may be the problem. The ERR_TUNNEL_CONNECTION_FAILED error is apparently a message Chrome gives when an HTTP proxy fails to forward a web socket request. You'll also need to make a similar change in development.rb: (Rack::LiveReload, :live_reload_port => 56789) In the Guardfile, add the :port option, like this: guard :livereload, :port => "56789" do You can try changing LiveReload to use a non-conflicting port. If you see something like this, it means another process/app is listening on that port: tcp4 0 0 *.35729 *.* LISTEN To check if this is the case, quit the guard process and then run: netstat -an | grep 35729 Perhaps some other process is listening on port 35729, resulting in the connection errors you are seeing in Chrome. Upgrade both to the latest version to be safe: bundle update guard-livereload rack-livereload Perhaps the version of guard-livereload (server) and rack-livereload (client) are incompatible. Possibility 1: incompatible LiveReload versions Here are some troubleshooting steps to take: I've checked to see whether there are other watchers on port 35729 and nothing obvious pops up.Īny pointers on how to get this working are appreciated! Thanks. I've tried this with e as well and still get the same error. Gem "guard-livereload", :require => falseĬ_after(ActionDispatch::Static, Rack::LiveReload) The changes I've made to my app that should enable this to work are: # Gemfile WebSocket connection to 'ws://localhost:35729/livereload' failed: Error in connection establishment: net::ERR_TUNNEL_CONNECTION_FAILED First the error (from Chrome): WebSocket connection to 'ws://localhost:35729/livereload' failed: Connection closed before receiving a handshake response Perhaps someone else can see what I'm missing. ![]() I'm having a bear of a time setting up live reload. ![]()
0 Comments
Leave a Reply. |