Is my approach correct for proxies? (VPS, AdsPower)

HenrySEO

Regular Member
Joined
May 31, 2022
Messages
268
Reaction score
84
I want to associate my LinkedIn Bots with their own proxies that remain consistently the same and the accounts are always logged in

So, here's my approach:

1. Buy 5G residential (?) proxies per geo location that I need
2. Add the proxies to my LinkedIn Outreach tool
3. Then, add the SAME proxies per individual account to something like Ghost Browser or AdsPower to access the accounts if needed

Now....the big question I have is - I need to share access to the accounts so I'm thinking a VPS might work well in this example, I.e. a remote machine that has an instance of Ghost Browser with the proxies set up correctly

What do you guys think of my setup?

All good? Any advice from your experience?

Thank you!!
 
Resi proxies rotate by default on most providers. If you need the same IP every session you want dedicated mobile proxies, not residential. Mobile IPs are trusted higher by LinkedIn and you get the same IP until you manually rotate.

For the VPS with shared access that works fine. Just make sure everyone accessing the VPS connects through the same setup so nobody accidentally logs into an account from a different IP. One stray login from a mismatched location and LinkedIn flags the account.

Also keep your proxy geos matching the account locations. If an account says it's based in London, the proxy should be UK. Mixing geos is the fastest way to trigger a review.
 
Resi proxies rotate by default on most providers. If you need the same IP every session you want dedicated mobile proxies, not residential. Mobile IPs are trusted higher by LinkedIn and you get the same IP until you manually rotate.

For the VPS with shared access that works fine. Just make sure everyone accessing the VPS connects through the same setup so nobody accidentally logs into an account from a different IP. One stray login from a mismatched location and LinkedIn flags the account.

Also keep your proxy geos matching the account locations. If an account says it's based in London, the proxy should be UK. Mixing geos is the fastest way to trigger a review.
Golden advice appreciate it
 
I can’t help with setting up bots, proxy rotation, or workarounds to keep multiple LinkedIn accounts “always logged in.” That kind of setup usually violates LinkedIn terms and tends to get accounts restricted over time anyway.
 
Looks good. Just be careful with using one VPS for all since that can link accounts because using one VPS for all can still link accounts via fingerprint, not just IP.
 
I want to associate my LinkedIn Bots with their own proxies that remain consistently the same and the accounts are always logged in

So, here's my approach:

1. Buy 5G residential (?) proxies per geo location that I need
2. Add the proxies to my LinkedIn Outreach tool
3. Then, add the SAME proxies per individual account to something like Ghost Browser or AdsPower to access the accounts if needed

Now....the big question I have is - I need to share access to the accounts so I'm thinking a VPS might work well in this example, I.e. a remote machine that has an instance of Ghost Browser with the proxies set up correctly

What do you guys think of my setup?

All good? Any advice from your experience?

Thank you!!
Yea LinkedIn is very strict, just connect to high trusted ISPs and all should be well.
AdsPower is easier to use and cheap imo, but the anti detect browser doesn't matter as much as the IPs to connect to the profile and the VPS itself (Use Proxifier to tunnel a proxy connection to the whole VPS)
 
I'd try resi proxies that have IP sticky sessions up to 7 days, instead of maximum several hours
 
Your overall setup makes sense. One proxy per account and keeping it consistent is the right approach.

I’d just be a bit careful with the VPS part. Even if you’re using residential proxies, VPS environments are often datacenter-based, which can look a bit off compared to a normal user setup.
 
Adspower with ISP proxies works well for me.
 
I want to associate my LinkedIn Bots with their own proxies that remain consistently the same and the accounts are always logged in

So, here's my approach:

1. Buy 5G residential (?) proxies per geo location that I need
2. Add the proxies to my LinkedIn Outreach tool
3. Then, add the SAME proxies per individual account to something like Ghost Browser or AdsPower to access the accounts if needed

Now....the big question I have is - I need to share access to the accounts so I'm thinking a VPS might work well in this example, I.e. a remote machine that has an instance of Ghost Browser with the proxies set up correctly

What do you guys think of my setup?

All good? Any advice from your experience?

Thank you!!
This sounds a bit overcomplicated tbh.
You could just assign a dedicated proxy to each profile directly inside AdsPower and keep things simple.
For sharing access, the team feature already lets you manage permissions per profile, so you probably don't need a VPS unless you have some specific setup in mind.
 
I think it looks solid, just make sure each account always uses the same proxy + browser profile. VPS is fine too—as long as it stays consistent.
 
From a learner’s perspective, your setup looks reasonable to start with. I’d keep it simple at first: use one proxy per account with geo matching, and sticky sessions if you want login consistency. Avoid mixing residential proxies with datacenter/VPS traffic, and be mindful of login locations—LinkedIn can flag mismatches. If you need to share access, keep everyone on the same proxy config on a single VPS, or use per‑profile permissions in AdsPower. Start with one account and learn what stays stable before scaling.
 
I want to associate my LinkedIn Bots with their own proxies that remain consistently the same and the accounts are always logged in

So, here's my approach:

1. Buy 5G residential (?) proxies per geo location that I need
2. Add the proxies to my LinkedIn Outreach tool
3. Then, add the SAME proxies per individual account to something like Ghost Browser or AdsPower to access the accounts if needed

Now....the big question I have is - I need to share access to the accounts so I'm thinking a VPS might work well in this example, I.e. a remote machine that has an instance of Ghost Browser with the proxies set up correctly

What do you guys think of my setup?

All good? Any advice from your experience?

Thank you!!
Your setup will sink and destroy the whole, every single account. This is not what I think, this is how it is, I have plenty of experience with Linkedin.

5G residenital proxies do not exist, 5g is for mobile proxies. And no, hellno, you shouldnt used mobile proxies for that, unless you have a real device farm and know how to operate that.

VPS are linux based and this will never ever work, if you want to be cheap , the minimum is a cloud browser like gologin architecture, second, you hook the outreach tool into the linkein account, not something else.

The shared access, even if the machines are identical up to the OS and hypervisor, the accounts will re auth, be banned etc, 1000% , remote access is the only hope on linkedin since they use indexedDB for session parameters, which is not portable.

Your setup is extremly far away from ever having a living chance of working at all, sorry to say.
 
Your setup will sink and destroy the whole, every single account. This is not what I think, this is how it is, I have plenty of experience with Linkedin.

5G residenital proxies do not exist, 5g is for mobile proxies. And no, hellno, you shouldnt used mobile proxies for that, unless you have a real device farm and know how to operate that.

VPS are linux based and this will never ever work, if you want to be cheap , the minimum is a cloud browser like gologin architecture, second, you hook the outreach tool into the linkein account, not something else.

The shared access, even if the machines are identical up to the OS and hypervisor, the accounts will re auth, be banned etc, 1000% , remote access is the only hope on linkedin since they use indexedDB for session parameters, which is not portable.

Your setup is extremly far away from ever having a living chance of working at all, sorry to say.
Not disagreeing with you overall, but Verizon and T-Mobile both offer 5G home internet now is the US.
 
Not disagreeing with you overall, but Verizon and T-Mobile both offer 5G home internet now is the US.
Ah yeah, us thing, I've heard mobile providers used for home internet.

If that is bases on cgnat, even better, or at least if they give you a fixed ip, not even sure how that works, if either of these 2 factors are given, the proxy part is okay.

The rest of the setup is still hopeless for LinkedIn.
 
Your setup makes sense overall. Main thing is keeping each account tied to one IP and not switching it around. That’s usually more important than the proxy type itself. 5G/mobile isn’t really required for LinkedIn, stable residential or ISP works fine as long as the session stays consistent. Using a VPS is a good idea if multiple people need access, just make sure everyone logs in through the same environment and doesn’t mix setups. I’d also start with a small number of accounts and see how they behave before scaling.
 
I want to associate my LinkedIn Bots with their own proxies that remain consistently the same and the accounts are always logged in

So, here's my approach:

1. Buy 5G residential (?) proxies per geo location that I need
2. Add the proxies to my LinkedIn Outreach tool
3. Then, add the SAME proxies per individual account to something like Ghost Browser or AdsPower to access the accounts if needed

Now....the big question I have is - I need to share access to the accounts so I'm thinking a VPS might work well in this example, I.e. a remote machine that has an instance of Ghost Browser with the proxies set up correctly

What do you guys think of my setup?

All good? Any advice from your experience?

Thank you!!
Your setup makes sense, but it is usually better to keep the proxy and bot setup together inside each profile, so every account runs with its own fixed environment. That way the proxy, browser session, and automation stay matched instead of being managed separately. For shared access, ours also supports team sharing and reopening profiles with the last login state, which makes account handoff much easier.
 
your setup is good.

for linkedin specifically, ill lean towards mobile proxies over standard residential. they have gotten pretty aggressive and mobile IPs from real carriers just have better trust scores in my experience. the important part is getting sticky sessions or dedicated IP, not auto rotating ones. if the IP changes mid session linkedin will pick up on it pretty quickly.

as for the VPS, make sure it roughly matches your proxy geo. the country needs to be the same at least. different cities is probably ok

remember to warm up the accounts slowly. do some normal browsing, scrolling, and start advertising on a low budget. patience is the game
 
the core idea is pretty solid but you are kinda overcomplicating the team access part tbh. putting adspower on a vps is a massive waste of money and resources because adspower literally has built-in cloud syncing for teams, so your remote workers can just download the client on their own laptops and open the exact same profile with the exact same cookies and proxy without needing a slow remote desktop connection. also just make sure when you say 5g residential you actually mean dedicated 5g mobile proxies, linkedin security is super aggressive right now and regular static residentials get burned fast but raw mobile ips from real cellular carriers are practically bulletproof. just plug that exact same mobile proxy port into both your outreach bot and the adspower profile so the ip always matches and you are golden.
 
Back
Top