Skip to content

Decodo Proxies Not Working with n8n-nodes-puppeteer #123

Description

@marekf93

Description of a problem

When I try to use Decodo proxies with n8n-nodes-puppeteer, all proxy configurations fail with a 401 error code. This occurs regardless of which proxy setup is used (user, HTTP, HTTPS, or SOCKS5).

Environment
Tool: n8n-nodes-puppeteer
Proxy Service: Decodo
Error: Request failed with status code 401

Steps to Reproduce

  1. Configure n8n-nodes-puppeteer with Decodo proxy credentials
  2. Set up operation (Get Page Content)
  3. Try different proxy configurations:

HTTP
HTTPS
SOCKS5
With user authentication

  1. Attempt to access a page that is definitely accessible

Current Behavior
All requests fail with a 401 error regardless of proxy configuration type.

I am attaching screenshots showing:

The n8n-nodes-puppeteer configuration interface with the proxy settings + the 401 error response received
The Decodo proxy management dashboard showing valid proxies

Is there a known compatibility issue between n8n-nodes-puppeteer and Decodo proxies or any special configuration requirements for Decodo proxies that aren't covered in the documentation? Could there be an authentication formatting issue when passing credentials to Puppeteer?

Thank you for any help..

Image
Image

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions