I'm using ngrok to put my web application online and make some tests. But, when I reload the page, the error ERR_NGROK_702 (Too Many Connections) appears, like the image below.
Is there any way to solve or avoid it instead of buying a paid plan?
How can I decrease the inbound connection volume, as said in the message?
Or the only way is to wait some minutes and try again?
I'll appreciate any suggestions.
You can use https://github.com/mmatczuk/go-http-tunnel it's self hosted open source ngrok alternative.
Just wait 1 minute or two and refresh. Optimize the number of connections made to the service or else pay to avoid this limitation.
Use Localtunnel insted of ngrok. https://theboroer.github.io/localtunnel-www/
You don't have to change the URL every time.
1) npm install -g localtunnel
2) lt --port 8081 --subdomain "your desired domain name"
eg: lt --port 8081 --subdomain myshopifyapp
Right now the tunnel provider (ngrok) has a limit of the number of connections or resources loaded in a given time. So, if you have a page with a lot of links to images, stylesheets, or scripts, you can go through the limit quickly.
Improving Live Links is something that we are wanting to do and are still working through the best way of going about this.
In the meantime, you have a couple of options:
Make use of a plugin to minify and/or lazy load assets so that the total number of assets is reduced for the various pages. Autoptimize 2 should help with this or a more advanced caching plugin like WP Rocket would also help.
Deploy a version of the site to a Demo site so that there aren’t any limits on the number of assets that are downloaded
Related
I recently purchased a new theme and installed wordpress on my GoDaddy hosting account for my portfolio. I am still working on it, but as of right now I sometimes get page load speeds of 10-20seconds, and others 2 seconds (usually after the page has been cached). I have done all that I believe I can (without breaking the site) to optimize my performance speed (reducing image sizing, using a free CDN, using W3 Total Cache, etc).
It seems that my main issue is this 'TTFB' wait time I get whenever I go to a new page that hasn't been cached yet. How I can fix this? Is it the theme's fault? Do I NEED to switch hosting providers? I really don't want to go through the hassle of doing that and paying So much more just to have less than optimal results. I am new to this.
My testing site:
http://test.ninamariephotography.com/
See my Web Page Results here:
http://www.webpagetest.org/result/161111_9W_WF0/
Thank you in advance to anyone for your help:)
Time To First Byte should depend on geography. I don't think that's your problem. I reran your test and got a B.
I think the issue is your hosting is a tiny shared instance, and you're serving static files. Here are some ideas to speed things up.
Serve images using an image-serving service. Check out imgix which is $3/m. It could help in unexpected ways serving images off an external domain depending on HTTP protocol version and browser version, and how connections are shared.
Try lossy compression. You lose some image detail, but you also lose some file size. Check out compressor.io for an easy tool.
Concatenate and minify scripts. You have a number of little javascript files that load individually. Consider joining them together and minifying. I don't know the tool chain for Wordpress, perhaps there's a setting?
If none of that helps, you should experiment with different a hosting choice.
I use mod_pagespeed on my Nginx-Webserver.
When I try to test some of my pages with Google Pagespeed Insights(https://developers.google.com/speed/pagespeed/insights) there are:
1) Many errors shown the first time I do this, when the page is not opened manually with a browser before.
2) At the second scan - or if I open my page manually with a browser before - Google Pagespeed Insights shows me 90+% instantly.
Some of my sites do not have very large traffic, cause they are niche specific. I do this speed-optimation mostly for ranking purpuses. Now I am worried that Google doesn't see the 90+% when they test my site, because the first scan shows 70-80% and many errors...
Ok... so I think mod_pagespeed purges its internal cache after a while and when the first one opens the site there are no optimized files and because optimation takes to much time, the first user gets some files without full optimation. Right?
My approach nr.1:
I have done some optimation so keep the cache for 12h, but my tests show me that it doesn't work. Are here any mistakes in my attempt?
#experimental mweber 400mb 12h
pagespeed FileCacheSizeKb 409600;
pagespeed FileCacheCleanIntervalMs 43200000;
pagespeed FileCacheInodeLimit 500000;
My approach nr.2:
My hoster give me the advice to warm up the cache with a wget-script, which opens my pages from time to time. I tried that but it doesn't show any effect, so are there any requirements or parameters I have to use with wget, so mod_pagespeeed starts optimation of files?
Would be great to get some tipps and advices from you! ty :)
wget will not trigger any caching, if caching was only triggered via request then wget would not access the files to trigger them anyway as it does not process html to trigger requests on the assets.
Why are you clearing the cache so soon?
I installed artifactory (2.6.5) at a linux server. Started it and now i want to configure some stuff over the webinterface. But the webinterface doesnt look like it should.
Only thing I edit after the installation was the default port in the jetty.xml file.
No idea what the reason for this look (see Screenshot) is. So any help is appreciated.
A couple of things could cause this:
Residual browser caches (very likely).
UI Resources blocked by the browser (quite unlikely).
The first case can be easily solved by clearing the browser's cache and re-loading the page.
The second case might require you to investigate which resources are being blocked (using the browser's console) and tweak the security settings/rules.
I just picked up a client who's Wordpress web site takes anywhere between 8 to 22 seconds to START loading. The loading delay also occurs when using the Wordpress backend so I'd like to fix the loading issue first before starting my work (template re-design). What's the quickest yet efficient way to determine why this Wordpress site is taking so long to start loading?
Thanks in advance
P.S. - They currently have a caching plugin installed (WP Super Cache) which I assume the previous web developer installed to help with the loading issue but it only helps with the front-end and not the back-end.
Try to run some test like YSlow and Google Page Speed and read their results and suggestions.
Google Speed Online is helping me a lot with analysis of my websites.
http://pagespeed.googlelabs.com/
I use browsermob. They use real browsers to test the site load performance. Shows very nice graphs showing how long each and every request took. Also shows how many requests happen in parallel. As they use real browser, you can see how long it will take to load on a real browser. Then you can choose from which location you want to test. You can choose a UK location to test how fast your page loads from UK.
By the way, I am in no way related to browsermob. I just happen to be a satisfied user of this.
And it is free.
Your server is probably loading far too many modules and is thrashing the disks as it's run out of memory.
You need to both reduce how much memory each PHP instance consumes and limit how many PHP instances can run simultanouesly to ensure you don't use virtual memory for your PHP instances.
I've written a detailed answer to a very similar problem here on Stack Overflow:
How can I figure out why my Wordpress pages load so slowly?
Well, i have came across a similar situation, such things happen when your website is hosted on a GridHosting server, which means it changes according to the server load, but sometimes the things are just opposite the scenario, the best way to check why it is slow is to first ping the website at random interval , so in this way you will know if the distance is the cause or the packet dropping is the issue, secondly, you need to make sure your server's configurations is good, i.e; request your host about a RAW log of your website, in this way you can know what is it taking long for your server to response, and the least best method is to check and make sure that your DNS resolves in a good time, and try to use some free CDN services like CloudFlare.
Hope this helps.
I have just installed the ACL and Content Access module. Imedietly after enabling them I was asked to rebuild the permissions. All perfectly normal I am told.
However, I set the 'rebuild' permissions page running about 40 minutes ago and it still says 'Initializing'. How long should it take? Am I doing something wrong?
The standard "rebuild perms" duration is roughly proportional to the number of node multiplied by the number of access modules enabled.
On a site with 100k nodes, you can easily take more than 24hours to rebuild permissions. Which means you simply don't want to do it interactively. But you can launch that rebuild from drush or use one of the faster non-standard rebuild methods.
To do it via drush, use:
drush php-eval 'node_access_rebuild();'
Just refresh the page. The perms get rebuilt in a few seconds :).
Note: If it takes you 24 hours to rebuild on a site with 100K nodes, something is wrong. It takes us about 30min on a site with 200K+ FWIW. For a smaller site it should be much less; I suspect you were experiencing an error of some kind.
A quick solution can be just change your theme back to default GARLAND theme and than try again rebuilding permissions, most probably it will work. As sometime it is JS errors which is causing it to stuck on Initialization.
And if your site has too much data (node like 100k , 200K) you can also use this script by placing it in a php file in Drupal root and running it. The code is under the heading
WSODs Due to Specific Modules -> Node Access
on this link :
http://drupal.org/node/158043