starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-26 01:06:00 +03:00

[GH-ISSUE #4936] [bug]: Agent versions (after v0.1.3) not working #1864

New issue

Closed

opened 2026-03-16 22:09:55 +03:00 by kerem · 7 comments

kerem commented

2026-03-16 22:09:55 +03:00

Owner

Originally created by @shaezard on GitHub (Mar 25, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4936

Is there an existing issue for this?

I have searched existing issues and this bug hasn't been reported yet

Current behavior

Some of the members in our team suddenly started seeing agent not working with the self hosted version of hoppscotch after they upgraded the agent. The last version working is v0.1.3
Also, when hoppscotch was updated to the latest version v2025.2.3 , even the version v0.1.3 of agent stopped working and the latest version of agent v0.1.7 also didn't work. As a result we had to downgrade both agent and hoppscotch to v0.1.3 and v2025.2.0 respectively.

Steps to reproduce

Deploy hoppscotch v2025.2.3
Try running agent v0.1.3 (Shouldn't work)
Try running agent v0.1.7 (Shouldn't work)
Deploy hoppscotch v2025.2.0
Try running agent v0.1.7 (Shouldn't work)
Try running agent v0.1.3 (Should work)

Logs and Screenshots

Environment

Production

Hoppscotch Version

Self-hosted

Interceptor

Agent - Web App

Browsers Affected

No response

Operating System

None

Additional Information

Originally created by @shaezard on GitHub (Mar 25, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4936 ### Is there an existing issue for this? - [x] I have searched existing issues and this bug hasn't been reported yet ### Current behavior Hi Some of the members in our team suddenly started seeing agent not working with the self hosted version of hoppscotch after they upgraded the agent. The last version working is v0.1.3 Also, when hoppscotch was updated to the latest version v2025.2.3 , even the version v0.1.3 of agent stopped working and the latest version of agent v0.1.7 also didn't work. As a result we had to downgrade both agent and hoppscotch to v0.1.3 and v2025.2.0 respectively. ### Steps to reproduce 1. Deploy hoppscotch v2025.2.3 2. Try running agent v0.1.3 (Shouldn't work) 3. Try running agent v0.1.7 (Shouldn't work) 1. Deploy hoppscotch v2025.2.0 2. Try running agent v0.1.7 (Shouldn't work) 3. Try running agent v0.1.3 (Should work) ### Logs and Screenshots ```shell ``` ### Environment Production ### Hoppscotch Version Self-hosted ### Interceptor Agent - Web App ### Browsers Affected _No response_ ### Operating System None ### Additional Information <img width="1234" alt="Image" src="https://github.com/user-attachments/assets/e6d69532-d352-416c-b1b8-3d413571b6d9" />

kerem

2026-03-16 22:09:55 +03:00

closed this issue
added the
bug

need testing
labels

kerem commented

2026-03-16 22:10:11 +03:00

Author

Owner

@liyasthomas commented on GitHub (Mar 26, 2025):

Hi @shaezard, unfortunately we couldn't reproduce this issue at our end. To better understand this scenario, can you answer these questions:

Make sure you've Hoppscotch Agent in your background process. Restart the process if it's not active in the background.

Make sure Hoppscotch Agent program is running in the background, either from the task bar or from background processes in task manager. Restart the process if not active.

Make sure you've registered your client with the Agent. This involves a one-time password verification:

Click retry to listen to the Agent process.

If the web app recognizes the Agent process, it will show Hoppscotch Agent is live. Click on the “+” button to register your web app client to the Agent.

The Agent will show a one-time activation code to authenticate the client registration.

Use this authentication code to activate the client.

Once the web app client is successfully registered, you'll see a registration ID

This is a one-time process.

Client registration with the Agent for every client (web app, desktop app, CLI) securely authenticates client's device flow to the platform.

Docs: https://docs.hoppscotch.io/documentation/features/interceptor

@liyasthomas commented on GitHub (Mar 26, 2025): Hi @shaezard, unfortunately we couldn't reproduce this issue at our end. To better understand this scenario, can you answer these questions: 1. Make sure you've Hoppscotch Agent in your background process. Restart the process if it's not active in the background. _Make sure Hoppscotch Agent program is running in the background, either from the task bar or from background processes in task manager. Restart the process if not active._ <img width="646" alt="Image" src="https://github.com/user-attachments/assets/05564e1f-eb4c-48a4-9878-db97a6442f05" /> --- 2. Make sure you've registered your client with the Agent. This involves a one-time password verification: _Click retry to listen to the Agent process._ <img width="646" alt="Image" src="https://github.com/user-attachments/assets/f25eb083-5cb3-4daa-87ec-72ee327b8a11" /> --- _If the web app recognizes the Agent process, it will show Hoppscotch Agent is live. Click on the “+” button to register your web app client to the Agent._ <img width="646" alt="Image" src="https://github.com/user-attachments/assets/fd52f324-a692-462e-84a4-dc010811ecdb" /> --- _The Agent will show a one-time activation code to authenticate the client registration._ <img width="646" alt="Image" src="https://github.com/user-attachments/assets/40377c72-d226-4bdb-a587-e5d00aa8ee26" /> --- _Use this authentication code to activate the client._ <img width="646" alt="Image" src="https://github.com/user-attachments/assets/e469bcbe-2283-4767-97f1-932357093346" /> --- _Once the web app client is successfully registered, you'll see a registration ID_ <img width="646" alt="Image" src="https://github.com/user-attachments/assets/ce9ad0f8-97d1-4dd8-a930-3b4bd03d1dbc" /> --- ### This is a one-time process. Client registration with the Agent for every client (web app, desktop app, CLI) securely authenticates client's device flow to the platform. Docs: https://docs.hoppscotch.io/documentation/features/interceptor

kerem commented

2026-03-16 22:10:16 +03:00

Author

Owner

@chhaviG22 commented on GitHub (Mar 26, 2025):

Hi @shaezard ,

I found out that the latest Hoppscotch app release needs the newest version of the Hoppscotch agent to work properly.
I was using an older agent version (v0.1.3), which wasn't compatible with the latest app version (v2025.2.3). After updating to the latest agent version (v0.1.7), I am able to connect successfully.

Additionally, the previous Hoppscotch app version does not work with v0.1.7 Hoppscotch agent, which suggests a breaking change in compatibility between app & agent versions.

So, to resolve this, you can ensure both the app & agent versions are updated to latest compatible versions.

@chhaviG22 commented on GitHub (Mar 26, 2025): Hi @shaezard , I found out that the latest Hoppscotch app release needs the newest version of the Hoppscotch agent to work properly. I was using an older agent version (v0.1.3), which wasn't compatible with the latest app version (v2025.2.3). After updating to the latest agent version (v0.1.7), I am able to connect successfully. Additionally, the previous Hoppscotch app version does not work with v0.1.7 Hoppscotch agent, which suggests a breaking change in compatibility between app & agent versions. So, to resolve this, you can ensure both the app & agent versions are updated to latest compatible versions.

kerem commented

2026-03-16 22:10:21 +03:00

Author

Owner

@shaezard commented on GitHub (Mar 26, 2025):

Thanks @chhaviG22
I used the latest version of hoppscotch agent with the latest release but still I'm not able to make it work. here's a screenshot showing the agent version and error that I receive when I send the request. This is on the official https://hoppscotch.io

@shaezard commented on GitHub (Mar 26, 2025): Thanks @chhaviG22 I used the latest version of hoppscotch agent with the latest release but still I'm not able to make it work. here's a screenshot showing the agent version and error that I receive when I send the request. This is on the official https://hoppscotch.io ![Image](https://github.com/user-attachments/assets/40898bef-f262-44fc-9939-5d06a722c648) ![Image](https://github.com/user-attachments/assets/213f6c96-3ab6-476c-9871-9ab77d150c6c)

kerem commented

2026-03-16 22:10:26 +03:00

Author

Owner

@shaezard commented on GitHub (Mar 26, 2025):

I was able to make it work after disabling the verify Peer setting on the Agent config. @liyasthomas Can you pls tell What exactly is peer and host in the agent settings.

@shaezard commented on GitHub (Mar 26, 2025): I was able to make it work after disabling the verify Peer setting on the Agent config. @liyasthomas Can you pls tell What exactly is peer and host in the agent settings.

kerem commented

2026-03-16 22:10:31 +03:00

Author

Owner

@CuriousCorrelation commented on GitHub (Mar 27, 2025):

Hi @chhaviG22, thanks for sharing your experience. You're right about the version compatibility between the Hoppscotch app and agent.

Just to add some context - we use a calver-like system for our app releases to support rapid development, faster iteration and evolution, like the current 2025.2.3 from March 19th.

The agent, however, uses a different versioning scheme (v0.1.x). The way agent releases work is to keep compatibility between it and cloud app:

For cloud users: The latest app (2025.2.3) needs the newest agent (v0.1.7)
For self-hosted: Each release as a mono-repo ships with a compatible agent version!

So each release makes sure compatibility between agent and the Hoppscotch calver-like release. Basically two different release cadences from the same codebase to support very wide variety of use cases like individuals, self-hosted at larger levels, and also at large enterprise.

For purely cloud based usage, you should use the latest agent with the live cloud app (this will be maintained with the Agent's auto-updater), and for purely self-hosted, simply match your self-hosted/self-built release with the version that's bundled with the release.

The desktop app actually solves this complexity very cleanly, since it bundles the agent machinery directly using relay with the Native interceptor, you don't have to worry about version cadence at all.

Thanks for bringing this up - it'll definitely help others who might run into the same issue!

@CuriousCorrelation commented on GitHub (Mar 27, 2025): Hi @chhaviG22, thanks for sharing your experience. You're right about the version compatibility between the Hoppscotch app and agent. Just to add some context - we use a calver-like system for our app releases to support rapid development, faster iteration and evolution, like the current `2025.2.3` from March 19th. The agent, however, uses a different versioning scheme (v0.1.x). The way agent releases work is to keep compatibility between it and cloud app: - For cloud users: The latest app (`2025.2.3`) needs the newest agent (`v0.1.7`) - For self-hosted: Each release as a mono-repo ships with a compatible agent version! So each release makes sure compatibility between agent and the Hoppscotch calver-like release. Basically two different release cadences from the same codebase to support very wide variety of use cases like individuals, self-hosted at larger levels, and also at large enterprise. For purely cloud based usage, you should use the latest agent with the live cloud app (this will be maintained with the Agent's auto-updater), and for purely self-hosted, simply match your self-hosted/self-built release with the version that's bundled with the release. The desktop app actually solves this complexity very cleanly, since it bundles the agent machinery directly using relay with the `Native` interceptor, you don't have to worry about version cadence at all. Thanks for bringing this up - it'll definitely help others who might run into the same issue!

kerem commented

2026-03-16 22:10:36 +03:00

Author

Owner

@CuriousCorrelation commented on GitHub (Mar 27, 2025):

Hi @shaezard, I may be able to help you out here. The "Verify Peer" and "Verify Host" settings in the Hoppscotch agent are certificate verification options:

"Verify Peer" when enabled checks that the server's SSL certificate is valid and trusted. It verifies the certificate was issued by a trusted Certificate Authority (CA) with the CA certs you may have applied from the agent's settings page. Disabling this skips this verification, which can help when working with self-signed certificates that were not applied in the agent's settings or internal servers with certificates you don't have direct access to.

"Verify Host" checks that the hostname in the URL matches the name in the server's SSL certificate. It prevents potential man-in-the-middle attacks where a valid certificate is presented but for a different domain than the one you're trying to access.

These two settings are typically used together for maximum security, but there are specific scenarios where you might need to adjust them separately. For example, in corporate environments where some microservices share the same certificate but have different hostnames, you might keep "Verify Peer" enabled but disable "Verify Host". Similarly, when working with development environments using wildcard certificates or services behind reverse proxies, these settings can be adjusted independently depending on your specific infrastructure setup.

That said, it's interesting that disabling these settings fixed your issue - this typically shouldn't be necessary for standard public endpoints. There might be something else going on.

If you're still troubleshooting, I'd recommend trying the Hoppscotch desktop app. The desktop app uses identical machinery to the agent (which will keep the network requests similar) and offers much better error reporting and diagnostic capabilities compared to the web app + agent, since it has deeper system access. This would help identify exactly what's causing the issue, as the desktop app can relay more detailed information about what went wrong during the connection attempt.

The extra diagnostics from the desktop app would be really helpful in understanding why that particular workaround was necessary in your case.

@CuriousCorrelation commented on GitHub (Mar 27, 2025): Hi @shaezard, I may be able to help you out here. The "Verify Peer" and "Verify Host" settings in the Hoppscotch agent are certificate verification options: "Verify Peer" when enabled checks that the server's SSL certificate is valid and trusted. It verifies the certificate was issued by a trusted Certificate Authority (CA) with the CA certs you may have applied from the agent's settings page. Disabling this skips this verification, which can help when working with self-signed certificates that were not applied in the agent's settings or internal servers with certificates you don't have direct access to. "Verify Host" checks that the hostname in the URL matches the name in the server's SSL certificate. It prevents potential man-in-the-middle attacks where a valid certificate is presented but for a different domain than the one you're trying to access. These two settings are typically used together for maximum security, but there are specific scenarios where you might need to adjust them separately. For example, in corporate environments where some microservices share the same certificate but have different hostnames, you might keep "Verify Peer" enabled but disable "Verify Host". Similarly, when working with development environments using wildcard certificates or services behind reverse proxies, these settings can be adjusted independently depending on your specific infrastructure setup. That said, it's interesting that disabling these settings fixed your issue - this typically shouldn't be necessary for standard public endpoints. There might be something else going on. If you're still troubleshooting, I'd recommend trying the Hoppscotch desktop app. The desktop app uses _identical machinery to the agent_ (which will keep the network requests similar) and offers much better error reporting and diagnostic capabilities compared to the web app + agent, since it has deeper system access. This would help identify exactly what's causing the issue, as the desktop app can relay more detailed information about what went wrong during the connection attempt. The extra diagnostics from the desktop app would be really helpful in understanding why that particular workaround was necessary in your case.

kerem commented

2026-03-16 22:10:41 +03:00

Author

Owner

@shaezard commented on GitHub (Mar 27, 2025):

Thanks for the elaborate explanation @CuriousCorrelation !! We found out the issue why it was only working after disabling the verify Peer setting on the Agent config. We had the CA Certificate for an internal proxy in the config but the proxy url was empty.

We tested the interceptors with different kind of hosts on our self hosted browser base hoppscotch and came up with the following conclusion:- (Note: This isn't appliacble to Desktop app)

hoppscotch release: 2025.2.3
Agent release: 0.1.7

if the host url is localhost:-

if the protocol is http
everything interceptor works apart from Browser
if the protocol is https
browser extension doesn't work - Is there way to make it work ?
agent - turn off verify host and verify Peer to make it work
agent with our internal proxy which sets Authorization Header - works

if the host is an external server, every interceptor works apart from Browser

@shaezard commented on GitHub (Mar 27, 2025): Thanks for the elaborate explanation @CuriousCorrelation !! We found out the issue why it was only working after disabling the verify Peer setting on the Agent config. We had the CA Certificate for an internal proxy in the config but the proxy url was empty. We tested the interceptors with different kind of hosts on our self hosted browser base hoppscotch and came up with the following conclusion:- (**Note: This isn't appliacble to Desktop app**) **hoppscotch release: 2025.2.3 Agent release: 0.1.7** if the host url is localhost:- 1. if the protocol is http everything interceptor works apart from Browser 2. if the protocol is https **browser extension doesn't work - Is there way to make it work ?** **agent - turn off verify host and verify Peer to make it work** agent with our internal proxy which sets Authorization Header - works if the host is an external server, every interceptor works apart from Browser

kerem referenced this issue

2026-03-17 01:08:23 +03:00

[PR #1864] [MERGED] multipart payload not working while using proxy #3531