Yep, the new site is up. Here is the information from James about the new site:
Just released the new website.. Woohoo, many weeks of testing..
Hopefully no issues.
I have migrated all the users over from the old SEREngines v1. If anyone has an issue, just drop me an email (team@serengines.com) with your paypal email and old API key and I will take a look into your account.
All existing SEREngines v1 users would have received an email with their new account details but their API key remains the same.
Note: you will need to however login and create more API keys for your other servers, as it is now 1 API key for 1 Server.
ALSO, you will need to be running GSA SER 11.92+, I will shut down the old API in a week or two.
Some New Features:
In the admin panel you can now add extra API keys (1 api key per server now) and also IP lock an API key to a specific server IP.
You can now see who is using your API keys and from what IP
Change API keys
View your invoices (for new invoices from today on)
Modify your current subscription to add more API Keys
@kxp - James just told me a minute ago about a bug.
The bug has been reported to Sven already, but here's what to do in the meantime to get it working for new users.
For new SEREngines users or Fresh GSA SER installs, it isn't creating the directory needed to install the engine files. So there is a quick fix until Sven pushes out SER 11.93.
Created a text document on Desktop and set the file path in "Save File"
On the "Options Tab":
All sections left as default except "Scheduled Posting"
On scheduled posting, have "Allow posting on same site again" checked.
Set all "Time to wait" options to 1 minute
Set "maximum posts per account" to 1 +/- 0
Set "Maximum accounts per site" to 100 +/- 0
I tried it with entering the Captcha manually, and using death by captcha. Basically, the same thing happens, it attempts to create an account once on mail.ru and once on yandex, then I just get a bunch of:
[ ] Attention! No targets to post to (no site list enabled, no engines allowing url extraction chosen)
Over and over in the log. I appreciate any tips you might have.
The "headless.exe" problem is back, it's been awhile. I'm using Greencloud VPS US SEO service. It's a Windows 2012 R2 Datacenter, 64bit, 3G memory and My GSA is 11.92.
I think it's been happening since GSA 11.90, but at that time it didn't happen very frequently, after a SERE update and GSA update, now it is crashing quite often, within 1 or 2 hours.
@everyone - There is a bug in headless causing some web 2.0s to fail. James said it will be fixed today.
@edge13 - After James logged into your VPS this is what he noticed:
"You ram usage is running dangerously high.
You only have 3GB of ram, and GSA is taking up nearly 1GB alone (because of the amount of threads you are using).
Your also running 500 threads.
I suspect the headless crash is happening because of your system being out of ram.
I also did a proxy check (unrelated to crash, I just saw some proxy errors in the logs), and 6/20 of your proxies are working.
So my suggestions would be to lower your thread count.. You shouldn't be running 500 threads with 6/20 proxies (not even if 20 proxies are working) or, get a machine with more ram + more proxies."
Thanks for the update --- touch wood but i saw no headless crash lately.
What i do notice is that when GSA SER closes unexpectedly, like when U close it with task manager, or running a update without stopping gsa ser first, -- then the Serengine threads are hanging, meaning if thought GSA SER is shut down, serengines threads can still be seen running in task manager. I normally END Task from within task manager. Its not a big problem and it sorts it self out when you restart gsa ser and start running projects again.
@everyone - James released the updated version of the SEREngines plugin (Headless) with the fixes including the one needed for mailru + will increase success rate of many other engines.
@royalmice - It won't happen with your setup because this issue is due to running out of memory.
I think the solution here would be to put some protection in place so if memory is getting full on a system, new jobs won't start (they will be retried later). As well as reporting the memory usage of Headless back to SER, so it can be controlled better. This is something I will chat with Sven about the best way to approach this.
Regarding the processes still running on SER crash - Yes this happens when SER itself is closed (crash or something), so when you restart SER and start the projects again, all the SEREngines processes will be closed.
I restarted my SER and decreased the amount of threads to 200. Regarding the proxies, which condition did you use to test them? I just tested them against Google search, all 20 are working. Please let me know if I need to update my proxies from squid proxy.
One more question: My email creator project has an error “No targets to post to (no site list enabled, no url extraction chosen" in my GSA, is that normal or there is something wrong with me settings of this project?
@edge13 - For me, I test my proxies using the anonymous test, not against Google since they are used to sign up for web 2.0's and not scraping.
Also, James told me that he found another bug in SER which is effecting mail.ru engines. Hopefully Sven can push an update for it soon. That might be what's causing your issue.
The "no targets to post to" would usually mean the "maximum accounts per site" number has been met, but its probably an issue caused by the bug.
I agree the fact that Serengines memory & CPU is not included in GSA SER, is a real problem, and something i raised several times to Jamese in the past and if not mistaken in the forum.
If Serengines mem and cpu usage was monitored by GSA ser, then i think the headless crashes can be prevented by auto lowering the threads when set mem and cpu usage is reached.
Using the below option when you have SERengines installed -- is pretty pointless as it does not include SERengine usage so it will NEVER be accurate.
Hope that @sven can look into including serengines usage in the stats.
On a positive side, the new Serengines website is really nice - a big step up from what it was before.
@przamunda Make sure you restart SER so it definitely gets the latest version of the SEREngines plugin. Also if you see a crash prompt, please PM me a screenshot or provide remote access to the VPS to take a look.
New problem: I was able to get an email generator project running. It looks like it was creating emails, but when I checked my save file on my desktop, it was filled with the file path over and over instead of the email credentials. Here are the contents of the file with my name replaced with "Username":
@everyone - Please update to SER version 11.93, and the latest SEREngines engines and the mail creator engines (mail.ru and yandex) should be saving to file correctly now
hey, haven't read all 855 posts yet... What engines are supported? Website lists 24 engines, why don't you list domain names?
I saw somewhere that {custom-subdomain}.wordpress.com is supported, is that correct? If so, this is fucking amazing good then let me know a fully engines list, cuz I will probably go buy in a light speed.
Trying it right now, is it me, or email creator makes like ~5 emails in an hour? 2captcha enabled, both mail.ru & yandex enabled. What should be the speed for email creators? What should be the speed for web 2.0 creators? How many threads should be set? You should document this, so that it's easy to find for new customers
CRITICAL BUG FOUND, it's confirmed: #trans_XX tags don't work on these web 2.0s! They work on typical engines, but not on yours. I have set up #trans_lt text here #notrans
@kxp kxp: Start a fresh email creator project, also make sure you have the latest version of the mail.ru engine.
@Gintas : Yes {custom-subdomain}.wordpress.com is supported, also a random theme is set and default posts removed. There is a variable in the project setup called "Blog Domain Name", make sure it is really unique so there isn't any failures in setting up the blog.
As for the email creator, it will create more than that per hour, just make sure you have fast proxies. It "naturally" creates accounts (mouse movements, real clicking, real keyboard typing) as to make accounts stick.
#trans_XX is something with GSA SER, I (James) will have to talk with Sven about that and see what is going on.
I have an engines request, if you would add these, all those other web 2.0 creators like rankerx or turboweb 2.0, fcs networker, etc. will become completely useless:
joomla.com - make sure verified url is not subdomain.joomla.com/category/post-name, but subdomain.joomla.com/category, cuz that post link is noindex & nofollow as I remember.
tumblr
over-blog
udemy - can put dofollow link in user's profile
viki.com can put a link in user's /about
speakerdeck
sparkfun
nature.com
These would make this tool frickin awesome. I can't wait to cancel rankerx and plug everything in one place - gsa ser
So I restarted SER, checked for updates on SEREngines (none found), and I separated mail.ru and Yandex into their own projects. Yandex continues creating email accounts, and the mail.ru project has no targets.
Is anyone else seeing abnormal CAPTCHA usage and reporting?
I watched for 5 minutes:
SER reports 12 captchas were sent to DBC DBC reports 96 were sent.
It's worth noting that's an exact multiple. Might be coincidence, but perhaps there is an inefficiency somewhere in the code?
I'm not running any other applications right now. I was surprised this morning when I received an email from DBC saying my balance was low. I ripped through 7,000 Catpcha solves in the last few days and have only generated about 400 email addresses.
@luca.vi: Yes, it picks a random theme, removes default posts and puts profile data where it can. Right now, version 2 doesn't put up a profile image but that will come soon.
I'm pretty sure there is definitely a Captcha issue here. I'm running 15
Yandex projects to get around the single thread limitation. In about 2
hours, SER ate ~5,000 DBC credits. That would be about 42 emails a minute.
It only created about 200 more, and I know there is no way that Only 15
email projects is running through that many credits in 2 hours. SER is only
registering about 500 Captcha requests in that time period.
Happy to report that @jamese has now fixed the headless crash issue i had. Now testing the new integration where SERengines RAM and CPU are reported to SER
Guys, for those who are having success with poster: what OS are you using? What proxies and from where?
I'm now testing 5 private proxies from buyproxies.org and constantly getting stuff like registration failed (JobCreation failed: connect_socket_in error The system cannof find the file specified).
@kxp : Would have to ask sven about the reporting on that one. I suspect (because of my experience with DBC) is that they are giving you the wrong captcha text and forcing SER to retry. You should use 2captcha instead because they are more accurate and also solve Recaptcha v2 (which many SEREngines web2.0s need)
@Gintas Mailru happens faster than that. Did you check your debug logs to see what the error was? It will retry, but if there is some issues it is having with registering (like your IP has been blocked) it will keep retrying and slow things down.
"JobCreation failed: connect_socket_in error The system cannof find the file specified" - Generally a ram issue, try a reboot this happens when it can't create anymore headless (SEREngines plugin) threads.
My email creator projects have still have the error “No targets to post to (no site list enabled, no url extraction chosen". They haven’t created anything at all.
I’ve updated gsa to 11.94 and updated serengin to the latest as well. There are separated 2 projects one for mail.ru and another for Yandex only. Option set like this:
@edge13 - I'll let James know. If you're using a VPS, you might want to shoot him an email and give VPS access. It's weird because I'm using the exact same settings, latest version, etc and I have a mail.ru project that has created around 500 emails and counting.
I'm using 2captcha for captcha solving and private proxies.
Regarding slow email creator, turns out I needed to lower "time to wait ..." on scheduled posting options, now it's faster. It's slow on default settings
Comments
Just released the new website.. Woohoo, many weeks of testing..
Hopefully no issues.
I have migrated all the users over from the old SEREngines v1. If anyone has an issue, just drop me an email (team@serengines.com) with your paypal email and old API key and I will take a look into your account.
All existing SEREngines v1 users would have received an email with their new account details but their API key remains the same.
Note: you will need to however login and create more API keys for your other servers, as it is now 1 API key for 1 Server.
ALSO, you will need to be running GSA SER 11.92+, I will shut down the old API in a week or two.
Some New Features:
In the admin panel you can now add extra API keys (1 api key per server now) and also IP lock an API key to a specific server IP.
You can now see who is using your API keys and from what IP
Change API keys
View your invoices (for new invoices from today on)
Modify your current subscription to add more API Keys
I've added the API key in SER and I don't see the beta engines in the Where to Submit list.
Any ideas?
The bug has been reported to Sven already, but here's what to do in the meantime to get it working for new users.
For new SEREngines users or Fresh GSA SER installs, it isn't creating the directory needed to install the engine files. So there is a quick fix until Sven pushes out SER 11.93.
Create this directory:
C:\Users\<current user>\AppData\Roaming\GSA Search Engine Ranker\engines
- I created a new project
- Uncheck all "Where to post to"
- Check both Yandex and Mail.ru
- Tried both public and private proxies.
- On the "Data" tab:
- Set URL to https://google.com because the project still requires a URL.
- Both "Login" and "Password" remain on "Randomize"
- Left Profile Image to default.
- Created a text document on Desktop and set the file path in "Save File"
- On the "Options Tab":
- All sections left as default except "Scheduled Posting"
- On scheduled posting, have "Allow posting on same site again" checked.
- Set all "Time to wait" options to 1 minute
- Set "maximum posts per account" to 1 +/- 0
- Set "Maximum accounts per site" to 100 +/- 0
I tried it with entering the Captcha manually, and using death by captcha. Basically, the same thing happens, it attempts to create an account once on mail.ru and once on yandex, then I just get a bunch of:[ ] Attention! No targets to post to (no site list enabled, no engines allowing url extraction chosen)
Over and over in the log. I appreciate any tips you might have.
@s4nt0s Can I send it to you?
Sure, I'll have to forward it to James and he can take a look at what's going on.
The same problem. i have send the support token id to you.
@edge13 - After James logged into your VPS this is what he noticed:
"You ram usage is running dangerously high.
You only have 3GB of ram, and GSA is taking up nearly 1GB alone (because of the amount of threads you are using).
Your also running 500 threads.
I suspect the headless crash is happening because of your system being out of ram.
I also did a proxy check (unrelated to crash, I just saw some proxy errors in the logs), and 6/20 of your proxies are working.
So my suggestions would be to lower your thread count.. You shouldn't be running 500 threads with 6/20 proxies (not even if 20 proxies are working) or, get a machine with more ram + more proxies."
Thanks for the update --- touch wood but i saw no headless crash lately.
What i do notice is that when GSA SER closes unexpectedly, like when U close it with task manager, or running a update without stopping gsa ser first, -- then the Serengine threads are hanging, meaning if thought GSA SER is shut down, serengines threads can still be seen running in task manager. I normally END Task from within task manager.
Its not a big problem and it sorts it self out when you restart gsa ser and start running projects again.
@royalmice - It won't happen with your setup because this issue is due to running out of memory.
I think the solution here would be to put some protection in place so if memory is getting full on a system, new jobs won't start (they will be retried later). As well as reporting the memory usage of Headless back to SER, so it can be controlled better. This is something I will chat with Sven about the best way to approach this.
Regarding the processes still running on SER crash - Yes this happens when SER itself is closed (crash or something), so when you restart SER and start the projects again, all the SEREngines processes will be closed.
I restarted my SER and decreased the amount of threads to 200. Regarding the proxies, which condition did you use to test them? I just tested them against Google search, all 20 are working. Please let me know if I need to update my proxies from squid proxy.
One more question: My email creator project has an error “No targets to post to (no site list enabled, no url extraction chosen" in my GSA, is that normal or there is something wrong with me settings of this project?
Thanks!
Also, James told me that he found another bug in SER which is effecting mail.ru engines. Hopefully Sven can push an update for it soon. That might be what's causing your issue.
The "no targets to post to" would usually mean the "maximum accounts per site" number has been met, but its probably an issue caused by the bug.
Thanks for keeping us updated. I too am still getting the "No targets to post to" error with my email project.
I agree the fact that Serengines memory & CPU is not included in GSA SER, is a real problem, and something i raised several times to Jamese in the past and if not mistaken in the forum.
If Serengines mem and cpu usage was monitored by GSA ser, then i think the headless crashes can be prevented by auto lowering the threads when set mem and cpu usage is reached.
Using the below option when you have SERengines installed -- is pretty pointless as it does not include SERengine usage so it will NEVER be accurate.
Hope that @sven can look into including serengines usage in the stats.
On a positive side, the new Serengines website is really nice - a big step up from what it was before.
@przamunda - Are you running the latest version?
@royalmice - That feature is already on the TODO list.
C:\Users\Username\Desktop\generated-emails.txtC:\Users\Username\Desktop\generated-emails.txtC:\Users\Username\Desktop\generated-emails.txtC:\Users\Username\Desktop\generated-emails.txtC:\Users\Username\Desktop\generated-emails.txtC:\Users\Username\Desktop\generated-emails.txtC:\Users\Username\Desktop\generated-emails.txtC:\Users\Username\Desktop\generated-emails.txtC:\Users\Username\Desktop\generated-emails.txtC:\Users\Username\Desktop\generated-emails.txtC:\Users\Username\Desktop\generated-emails.txt
What should be the speed for email creators?
What should be the speed for web 2.0 creators?
How many threads should be set?
You should document this, so that it's easy to find for new customers
Yandex is running fine. I'm not seeing any mail.ru being saved in the file and when I look at the targets, mail.ru is not present in the list.
Screenshots send to @JAMESE
@kxp kxp: Start a fresh email creator project, also make sure you have the latest version of the mail.ru engine.
@Gintas : Yes {custom-subdomain}.wordpress.com is supported, also a random theme is set and default posts removed. There is a variable in the project setup called "Blog Domain Name", make sure it is really unique so there isn't any failures in setting up the blog.
As for the email creator, it will create more than that per hour, just make sure you have fast proxies. It "naturally" creates accounts (mouse movements, real clicking, real keyboard typing) as to make accounts stick.
#trans_XX is something with GSA SER, I (James) will have to talk with Sven about that and see what is going on.
- joomla.com - make sure verified url is not subdomain.joomla.com/category/post-name, but subdomain.joomla.com/category, cuz that post link is noindex & nofollow as I remember.
- tumblr
- over-blog
- udemy - can put dofollow link in user's profile
- viki.com can put a link in user's /about
- speakerdeck
- sparkfun
- nature.com
These would make this tool frickin awesome. I can't wait to cancel rankerx and plug everything in one place - gsa serSo I restarted SER, checked for updates on SEREngines (none found), and I separated mail.ru and Yandex into their own projects. Yandex continues creating email accounts, and the mail.ru project has no targets.
@everyone - The memory and cpu usage of the SEREngines plugin will be included in SER 11.94.
So now memory/thread management will work.
@Gintas: Joomla and Tumblr are being worked on already. Will also look at the other ones. Also thanks for the tip with Joomla
@Royalmice: Fixed crashing bug with SEREngines plugin on some servers.
I watched for 5 minutes:
SER reports 12 captchas were sent to DBC
DBC reports 96 were sent.
It's worth noting that's an exact multiple. Might be coincidence, but perhaps there is an inefficiency somewhere in the code?
I'm not running any other applications right now. I was surprised this morning when I received an email from DBC saying my balance was low. I ripped through 7,000 Catpcha solves in the last few days and have only generated about 400 email addresses.
@luca.vi: Yes, it picks a random theme, removes default posts and puts profile data where it can. Right now, version 2 doesn't put up a profile image but that will come soon.
Now testing the new integration where SERengines RAM and CPU are reported to SER
Things are moving forward ===>
Random thought: could it be failing so much because we are all using the same username generator, so most of the usernames are taken?
what OS are you using?
What proxies and from where?
I'm now testing 5 private proxies from buyproxies.org and constantly getting stuff like registration failed (JobCreation failed: connect_socket_in error The system cannof find the file specified).
Only about 200 were reported as incorrect in the DBC dashboard and there were only double digits reported in SER as incorrect.
My email creator projects have still have the error “No targets to post to (no site list enabled, no url extraction chosen". They haven’t created anything at all.
I’ve updated gsa to 11.94 and updated serengin to the latest as well. There are separated 2 projects one for mail.ru and another for Yandex only. Option set like this:
Any idea why it doesn't work?
Cheers!
I'm using 2captcha for captcha solving and private proxies.