# Forge remote not working **URL:** \ **Category:** Forge\ **Tags:** forge-remote\ **Created:** [February 16, 2024, 5:34am UTC](https://community.developer.atlassian.com/t/forge-remote-not-working/77359 "2024-02-16T05:34:26Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![YvesIvadHABIMANA](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/yvesivadhabimana/32/50131_2.png) [@YvesIvadHABIMANA](https://community.developer.atlassian.com/u/YvesIvadHABIMANA)\ **Post date:** [February 16, 2024, 5:34am UTC](https://community.developer.atlassian.com/t/forge-remote-not-working/77359/1 "2024-02-16T05:34:26Z")
I wanted to use Forge remote to have my forge app connect to a Netflify function but I can’t seem to get it to work. I tried to folllow the documentation and my manifest looks like the folllowing ```auto modules: jira:issuePanel: - key: user-by-reference-group title: User reference by group icon: https://developer.atlassian.com/platform/forge/images/icons/issue-panel-icon.svg resource: trigger-resources resolver: endpoint: create-user-api-endpoint function: - key: trigger-function handler: index.run endpoint: - key: create-user-api-endpoint remote: create-user-api-func resources: - key: trigger-resources path: static/dist tunnel: port: 3000 permissions: content: styles: - unsafe-inline scopes: [] remotes: - key: create-user-api-func baseUrl: https://user-group-reference.netlify.app app: id: ari:cloud:ecosystem::app/597aae01-e322-4c97-a926-f18cd7124f3a ``` somewhere in my code I am trying to invoke the remote like the following ```auto const handleClick = async () => { try { const response = await invokeRemote({ method: "GET", path: "/api/forge", }); setData(JSON.stringify(response)); } catch (error: any) { setData(error); } }; ``` But nothing is happening. I also tried to install the [demo application](https://bitbucket.org/atlassian/forge-remote-app/src/main/) that [mentioned in the documentation](https://developer.atlassian.com/platform/forge/forge-remote-overview/#reference-applications) and it doesn’t work either. Am I doing something wrong or Forge remote features doesn’t work at all? ---
**Author:** ![Berkayztrk](https://avatars.discourse-cdn.com/v4/letter/b/ccd318/32.png) [@Berkayztrk](https://community.developer.atlassian.com/u/Berkayztrk)\ **Post date:** [February 16, 2024, 1:51pm UTC](https://community.developer.atlassian.com/t/forge-remote-not-working/77359/2 "2024-02-16T13:51:29Z")
Hello @YvesIvadHABIMANA, I am also using Forge Remote and it works fine without any problems. Your manifest file looks correct to me. Are you sure that the latest version of your code is deployed and running? Can you place some `console.log` lines to see what is happening? ```auto const handleClick = async () => { try { console.log("Sending request..."); const response = await invokeRemote({ method: "GET", path: "/api/forge", }); console.log("Result:", response); setData(JSON.stringify(response)); } catch (error: any) { console.log("Error:", error); setData(error); } }; ``` ---
**Author:** ![YvesIvadHABIMANA](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/yvesivadhabimana/32/50131_2.png) [@YvesIvadHABIMANA](https://community.developer.atlassian.com/u/YvesIvadHABIMANA)\ **Post date:** [February 16, 2024, 2:15pm UTC](https://community.developer.atlassian.com/t/forge-remote-not-working/77359/3 "2024-02-16T14:15:50Z")
Hello @Berkayztrk I have tried to log, but since my code is running from a Custom UI environment using React. I was not able to see the logs. I tried to display the response in the UI by rendering the stringfied state using `JSON.stringify(data)` but I always get an empty object as output ---
**Author:** ![Berkayztrk](https://avatars.discourse-cdn.com/v4/letter/b/ccd318/32.png) [@Berkayztrk](https://community.developer.atlassian.com/u/Berkayztrk)\ **Post date:** [February 16, 2024, 2:37pm UTC](https://community.developer.atlassian.com/t/forge-remote-not-working/77359/4 "2024-02-16T14:37:27Z")
You should be able to see the logs in your browser’s dev tools console. I also use Custom UI & React and can see the log outputs in the browser console. ---
**Author:** ![YvesIvadHABIMANA](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/yvesivadhabimana/32/50131_2.png) [@YvesIvadHABIMANA](https://community.developer.atlassian.com/u/YvesIvadHABIMANA)\ **Post date:** [February 16, 2024, 2:43pm UTC](https://community.developer.atlassian.com/t/forge-remote-not-working/77359/5 "2024-02-16T14:43:54Z")
I am only able to see logs when I don’t use anything from `@forge/bridge` when I do I get the following error ![Screenshot 2024-02-16 at 16.42.18](https://global.discourse-cdn.com/atlassiandeveloper/original/3X/6/9/69cc28da9cc235714d43d73317f6329e9f283d5a.png) ---
**Author:** ![YvesIvadHABIMANA](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/yvesivadhabimana/32/50131_2.png) [@YvesIvadHABIMANA](https://community.developer.atlassian.com/u/YvesIvadHABIMANA)\ **Post date:** [February 16, 2024, 3:18pm UTC](https://community.developer.atlassian.com/t/forge-remote-not-working/77359/6 "2024-02-16T15:18:45Z")
I inspected using [graphql dev tools](https://chromewebstore.google.com/detail/graphql-developer-tools/hflnkihcpgldmkepajmpooacmmhglpff) and I get the following error ```auto { "data": { "invokeExtension": { "success": false, "response": null, "contextToken": null, "errors": [ { "message": "Invalid response from remote", "extensions": { "errorType": "INVALID_REMOTE_INVOCATION_ERROR", "statusCode": 400, "__typename": "GenericMutationErrorExtension" }, "__typename": "MutationError" } ], "__typename": "InvokeExtensionResponse" } }, "extensions": { "gateway": { "request_id": "174e9474718242a7aebe1d09ac013589", "crossRegion": false, "edgeCrossRegion": false } } } ``` ---
**Author:** ![Berkayztrk](https://avatars.discourse-cdn.com/v4/letter/b/ccd318/32.png) [@Berkayztrk](https://community.developer.atlassian.com/u/Berkayztrk)\ **Post date:** [February 16, 2024, 3:37pm UTC](https://community.developer.atlassian.com/t/forge-remote-not-working/77359/7 "2024-02-16T15:37:53Z")
It looks like your backend endpoint returns an invalid response. What is the format of the response expected to be returned from the Netlify url? ---
**Author:** ![YvesIvadHABIMANA](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/yvesivadhabimana/32/50131_2.png) [@YvesIvadHABIMANA](https://community.developer.atlassian.com/u/YvesIvadHABIMANA)\ **Post date:** [February 16, 2024, 3:57pm UTC](https://community.developer.atlassian.com/t/forge-remote-not-working/77359/8 "2024-02-16T15:57:46Z")
It can return anything. I am currently just returning a json object ![Screenshot 2024-02-16 at 17.55.23](https://global.discourse-cdn.com/atlassiandeveloper/original/3X/5/f/5f9b1c89a7d4d72f1321c7341b1b19ca8db3dbc8.png) ---
**Author:** ![YvesIvadHABIMANA](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/yvesivadhabimana/32/50131_2.png) [@YvesIvadHABIMANA](https://community.developer.atlassian.com/u/YvesIvadHABIMANA)\ **Post date:** [February 17, 2024, 9:53am UTC](https://community.developer.atlassian.com/t/forge-remote-not-working/77359/9 "2024-02-17T09:53:37Z")
I managed to get it to work. I needed to also register the path I was trying to get. here is the changes I made in the manifest file ```auto - key: create-user-api-endpoint remote: create-user-api-func route: path: /.netlify/functions/forge auth: appUserToken: enabled: true appSystemToken: enabled: true ``` ---
**Author:** ![JakubStawiszynski](https://avatars.discourse-cdn.com/v4/letter/j/977dab/32.png) [@JakubStawiszynski](https://community.developer.atlassian.com/u/JakubStawiszynski)\ **Post date:** [October 10, 2025, 8:20am UTC](https://community.developer.atlassian.com/t/forge-remote-not-working/77359/10 "2025-10-10T08:20:53Z")
I just wanted to leave a comment that we experienced a similar issue, and for us, the problem was resolved after removing the **`appSystemToken`** and using only the **`appUserToken`** in the endpoint declaration.