We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I see a number of these in my logs:
Sikka: IP Blocked. 66.249.73.237 Sikka: Closing current connection [the connection id from meteor.connection]
When I do a whois lookup on 66.249.73.237 I see that it belongs to Google.
66.249.73.237
Now I wonder, am I blocking google bots? Does Sikka have adverse affects on SEO?
Additionally, it would be really nice to see exactly why Sikka has blocked an IP.
I doubt Google has some kind of vendetta against me so it has been DDoS'ing my small meteor site :)
The text was updated successfully, but these errors were encountered:
Pure Meteor is not SEO friendly, you need something like phantom.js or server-side-render.
Sorry, something went wrong.
This is not about seo, this is about sikka blocking legitimate requests from the most legitimate ip block on the internet.
@serkandurusoy just increase the ip limit 20 is really low. 100+ should be good. But an option to white list well known IPs is better...
No branches or pull requests
I see a number of these in my logs:
When I do a whois lookup on
66.249.73.237
I see that it belongs to Google.Now I wonder, am I blocking google bots? Does Sikka have adverse affects on SEO?
Additionally, it would be really nice to see exactly why Sikka has blocked an IP.
I doubt Google has some kind of vendetta against me so it has been DDoS'ing my small meteor site :)
The text was updated successfully, but these errors were encountered: