BUG_Failed to get accessToken, Network request failed

[kjakobczyk]

Describe the bug
I'm trying to use Abacus with Firefly III server v.5.7.9 running on Docker via docker-compose.

To Reproduce
Steps to reproduce the behavior:

1. Create new OAuth token in Firefly III
2. Open Abacus for Firefly III
3. Fill the backend URL and Client ID in Abacus for Firefly III leaving client secret empty
4. Click on "Sign in" button
5. Log in to Firefly III
6. Click on "Authorize" in Firefly III
7. You see the error message saying that "Something went wrong" with description "failed to get accessToken, Network request failed.

Expected behavior
After clicking on "Authorize" in Firefly III I'd expect the application to log me in and allow to insert information to my Firefly III instance through Abacus for Firefly.

Screenshots

Smartphone (please complete the following information):

• Device: iPhone 13
• OS: iOS 16
• Firefly III v5.7.9 running in Docker behind Apache2 reverse proxy
• Latest Abacus for Firefly III

[victorbalssa]

Do you have any errors after step 6?

What happen after step 6? safari close the current connexion and you get the red notification?
If that's the case, can you look at your Firefly III logs and display what errors you may have?

[nick4333]

It's not self signed. It's signed by OpenSSL, which is an open source trusted CA that allows you to get a signed cert for free.

[victorbalssa]

@nick4333
Personal Access Token should work

[nick4333]

It doesn't, it's related to the reverse proxy as connecting directly by IP, as others have noted, works correctly with no issues. I have tried multiple times with a personal access token, disabling the tls certificates, and the only way I could get it to work was unsecure http, bypassing the reverse proxy.

My config isn't doing anything crazy either, just setting a forwarded for ip header, then sending the rest of the request to the application.

[victorbalssa]

@nick4333 I'm not sure how to debug this, a Personal Access Token is set in the Authorization header, if you forward it correctly and don't change the payload it should work normally 🤔

[danielriddell21]

@victorbalssa was there ever a resolution to @nick4333 ’s issue.

I seem to be experiencing the same thing

[bbgth]

@victorbalssa I am having trouble connecting to my firefly (docker) server via nginx reverse proxy. It was working in v0.11.2 (OTA) but when v0.12.4 was released, I get "Something went wrong. Failed to get accessToken, Network request failed"

I am running iOS 17 on 2 devices, and iOS 16 on another device. All having the same issues

I am able to connect if I use direct IP:Port and bypass nginx.

No SSL usage. HTTP only since it is running locally

No changes to nginx config since v0.11.2

nginx logs:

"GET /oauth/authorize?code_challenge=&code_challenge_method=&client_secret=&redirect_uri=abacusfiiiapp%3A%2F%2Fredirect&client_id=&response_type=code&state=HTTP/1.1" 302 5 "-" ""

That's it.

Nginx config:

server {
listen 80;
server_name ;
location / {
proxy_pass http://<redacted. docker name>:8080/;
proxy_redirect off;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Server $host;
}
}

I have also tried "Personal Access Token". It didn't even seem to hit the server. No log entry whatsoever.

Thoughts?

[danielriddell21]

I have the exact same issue. I am behind Authentik using Traefik.

I am using https, but using a PAT doesnt seem to hit the server at all

I have made sure and can confirm the api paths are bypassed. Its almost like the app isnt sending a request when using PAT

[victorbalssa]

I will need some time to fix this we can follow it here #256

[bbgth]

@victorbalssa for me, PAT doesn’t hit server and normal OAUTH using client ID and client Secret (my previous v0.11.2) method no longer works with "Something went wrong. Failed to get accessToken, Network request failed" error

Just want to make sure this is captured too. #256 seems to be only for PAT issue

[bbgth]

@victorbalssa I’ve done a bit more testing. I noticed if I access it directly via IP, it works (http://123.456.789.1:1234)

port 1234 is directly pointed to the firefly docker container and doesn’t go through nginx reverse proxy

http://firefly.domain.tld:1234 where firefly.domain.tld is resolved to IP 123.456.789.1 doesn’t work despite it doesn’t go through nginx reverse proxy as well.

http://firefly.domain.tld where firefly.domain.tld is resolved to IP 123.456.789.1 doesn’t work. This url goes through nginx reverse proxy which was working in a prior Abacus version.

Note: this is all on http (no ssl) since it is all only locally accessible

Note 2: firefly latest docker image

Note 3: this affects BOTH PAT AND OAUTH

Note 4: IP address is a local lan IP. Not an internet routable IP. DNS is resolved using local dns resolver (with custom dns names)

[paulcalabro]

I actually did pretty much the same test @bbgth did to troubleshoot #256 and arrived at the same results myself.
I noticed I saw no traffic via Burp Suite when using the "Log In" button, but saw traffic when clicking the "Create a new PAT" link
above, which is opened independently in a browser. I too am use local LAN IP with a local DNS resolver with custom DNS resource records. When I swapped out the hostname for an IP address and used a NC listener, I saw traffic.