github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-06 15:12:35 -05:00
Code Issues 1.5k Packages Projects Releases 54 Wiki Activity

[Bug]: Have to clear cookies every day in order to sync with bank #983

New Issue
Closed
opened 2026-02-28 19:27:13 -06:00 by GiteaMirror · 23 comments
GiteaMirror commented 2026-02-28 19:27:13 -06:00
Owner
Copy Link

Originally created by @crispybegs on GitHub (Mar 12, 2024).

Verified issue does not already exist?

  • I have searched and found no existing issue

Is this related to GoCardless, Simplefin or another bank-sync provider?

  • I have checked my server logs and could not see any errors there
  • I will be attaching my server logs to this issue
  • I will be attaching my client-side (browser) logs to this issue
  • I understand that this issue will be automatically closed if insufficient information is provided

What happened?

my bank sync via gocardless works perfectly, but every day, when I open Actual, the Sync option is greyed out and in order to get it working again I need to clear cookies for the session and log in all over again. This happens every morning, on each device i use - desktop / laptop / mobile.

What am i getting wrong here?

What error did you receive?

sync button greyed out

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Chrome, Safari

Operating System

Mac OSX

Originally created by @crispybegs on GitHub (Mar 12, 2024). ### Verified issue does not already exist? - [X] I have searched and found no existing issue ### Is this related to GoCardless, Simplefin or another bank-sync provider? - [ ] I have checked my server logs and could not see any errors there - [ ] I will be attaching my server logs to this issue - [ ] I will be attaching my client-side (browser) logs to this issue - [ ] I understand that this issue will be automatically closed if insufficient information is provided ### What happened? my bank sync via gocardless works perfectly, but every day, when I open Actual, the Sync option is greyed out and in order to get it working again I need to clear cookies for the session and log in all over again. This happens every morning, on each device i use - desktop / laptop / mobile. What am i getting wrong here? ### What error did you receive? sync button greyed out ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Chrome, Safari ### Operating System Mac OSX
GiteaMirror added the bug label 2026-02-28 19:27:13 -06:00
GiteaMirror commented 2026-02-28 19:27:14 -06:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Mar 12, 2024):

what does the server status in the top right say when you cant sync?

@youngcw commented on GitHub (Mar 12, 2024): what does the server status in the top right say when you cant sync?
GiteaMirror commented 2026-02-28 19:27:14 -06:00
Author
Owner
Copy Link

@crispybegs commented on GitHub (Mar 12, 2024):

what does the server status in the top right say when you cant sync?

um, i can't seem to replicate the situation right now, but I seem to recall from last week when this first started happening that it was disconnected from the server. I can't recall the exact syntax of the message, but I can check tomorrow morning when it happens again.

@crispybegs commented on GitHub (Mar 12, 2024): > what does the server status in the top right say when you cant sync? um, i can't seem to replicate the situation right now, but I seem to recall from last week when this first started happening that it was disconnected from the server. I can't recall the exact syntax of the message, but I can check tomorrow morning when it happens again.
GiteaMirror commented 2026-02-28 19:27:14 -06:00
Author
Owner
Copy Link

@crispybegs commented on GitHub (Mar 12, 2024):

oh there we go

Screenshot 2024-03-12 at 18 09 08 Screenshot 2024-03-12 at 18 09 12

the server's not offline, obviously. If i clear the cache and log in again, it will be working

@crispybegs commented on GitHub (Mar 12, 2024): oh there we go <img width="288" alt="Screenshot 2024-03-12 at 18 09 08" src="https://github.com/actualbudget/actual/assets/129169122/8c80efec-5e0a-4719-998e-30a497237315"> <img width="308" alt="Screenshot 2024-03-12 at 18 09 12" src="https://github.com/actualbudget/actual/assets/129169122/23c9f240-ee76-4593-b44b-8c8194b26a88"> the server's not offline, obviously. If i clear the cache and log in again, it will be working
GiteaMirror commented 2026-02-28 19:27:15 -06:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Mar 12, 2024):

do you have anything tricky happening like auto clearing the browser cache or adding authentication in front of the server?

@youngcw commented on GitHub (Mar 12, 2024): do you have anything tricky happening like auto clearing the browser cache or adding authentication in front of the server?
GiteaMirror commented 2026-02-28 19:27:15 -06:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Mar 12, 2024):

"Server offline" label is shown either if connection to the server cannot be established (i.e. no network access) or if the server is not accepting your auth token (you get this when logging in).

Check the network logs when opening the page - if it's auth issue you will see a failed API call (403 I think). If that's the case then something interesting is happening in your server instance. Something is dropping your auth table and recreating. Which is weird.. it might also mean your transaction changes are also being deleted from the server (check this by opening an incognito tab and logging in - do you see files on the server? Do this AFTER you see the "server offline" button but BEFORE re-logging into the server from your non-incognito window).

@MatissJanis commented on GitHub (Mar 12, 2024): "Server offline" label is shown either if connection to the server cannot be established (i.e. no network access) or if the server is not accepting your auth token (you get this when logging in). Check the network logs when opening the page - if it's auth issue you will see a failed API call (403 I think). If that's the case then something interesting is happening in your server instance. Something is dropping your auth table and recreating. Which is weird.. it might also mean your transaction changes are also being deleted from the server (check this by opening an incognito tab and logging in - do you see files on the server? Do this AFTER you see the "server offline" button but BEFORE re-logging into the server from your non-incognito window).
GiteaMirror commented 2026-02-28 19:27:16 -06:00
Author
Owner
Copy Link

@crispybegs commented on GitHub (Mar 13, 2024):

do you have anything tricky happening like auto clearing the browser cache or adding authentication in front of the server?

thanks all. yes my actual instance is accessed via a cloudflare tunnel, which has a rule in front of it that requires my email address to receive a OTP to then gain access to actual.

However, i can always access the UI, it's just the server is marked as offline once i get there.
No browser cache clearing or anything like that. Also, this only started happenign recently. I've always had the same set up and it didn't used to do this, so I'm befuddled.

to add to this, every time I go through this process and log back in again from scratch, my preferences have been reset.. for example my dates are reset to MM/DD/YYY, even though I set them to DD/MM/YYYY every day

Screenshot 2024-03-13 at 13 22 51
@crispybegs commented on GitHub (Mar 13, 2024): > do you have anything tricky happening like auto clearing the browser cache or adding authentication in front of the server? thanks all. yes my actual instance is accessed via a cloudflare tunnel, which has a rule in front of it that requires my email address to receive a OTP to then gain access to actual. However, i can always access the UI, it's just the server is marked as offline once i get there. No browser cache clearing or anything like that. Also, this only started happenign recently. I've always had the same set up and it didn't used to do this, so I'm befuddled. to add to this, every time I go through this process and log back in again from scratch, my preferences have been reset.. for example my dates are reset to MM/DD/YYY, even though I set them to DD/MM/YYYY every day <img width="564" alt="Screenshot 2024-03-13 at 13 22 51" src="https://github.com/actualbudget/actual/assets/129169122/9c8c04be-d34f-44c1-ab2b-a5540056b556">
GiteaMirror commented 2026-02-28 19:27:16 -06:00
Author
Owner
Copy Link

@shall0pass commented on GitHub (Mar 13, 2024):

Just a thought on what might be happening. There was a recent improvement to allow PWA support to work offline. If your authentication is failing in some way or of the PWA just can't see the server, the PWA would still work but as an offline application. Any settings that are only accessible when the server is connected wouldn't be available... which I believe includes secrets for bank sync integrations.

@shall0pass commented on GitHub (Mar 13, 2024): Just a thought on what _might_ be happening. There was a recent improvement to allow PWA support to work offline. If your authentication is failing in some way or of the PWA just can't see the server, the PWA would still work but as an offline application. Any settings that are only accessible when the server is connected wouldn't be available... which I believe includes secrets for bank sync integrations.
GiteaMirror commented 2026-02-28 19:27:17 -06:00
Author
Owner
Copy Link

@crispybegs commented on GitHub (Mar 13, 2024):

Just a thought on what might be happening. There was a recent improvement to allow PWA support to work offline. If your authentication is failing in some way or of the PWA just can't see the server, the PWA would still work but as an offline application. Any settings that are only accessible when the server is connected wouldn't be available... which I believe includes secrets for bank sync integrations.

hmm, although this is happening on my desktop & laptop?

@crispybegs commented on GitHub (Mar 13, 2024): > Just a thought on what _might_ be happening. There was a recent improvement to allow PWA support to work offline. If your authentication is failing in some way or of the PWA just can't see the server, the PWA would still work but as an offline application. Any settings that are only accessible when the server is connected wouldn't be available... which I believe includes secrets for bank sync integrations. hmm, although this is happening on my desktop & laptop?
GiteaMirror commented 2026-02-28 19:27:17 -06:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Mar 13, 2024):

are you leaving the web page open then coming back to it? It sounds like no, but just to be sure.

@youngcw commented on GitHub (Mar 13, 2024): are you leaving the web page open then coming back to it? It sounds like no, but just to be sure.
GiteaMirror commented 2026-02-28 19:27:17 -06:00
Author
Owner
Copy Link

@jfdoming commented on GitHub (Mar 13, 2024):

Just a thought on what might be happening. There was a recent improvement to allow PWA support to work offline. If your authentication is failing in some way or of the PWA just can't see the server, the PWA would still work but as an offline application. Any settings that are only accessible when the server is connected wouldn't be available... which I believe includes secrets for bank sync integrations.

hmm, although this is happening on my desktop & laptop?

I believe the offline PWA support that was added works whether or not you actually install the app. Maybe we need a setting toggle to disable offline support? Or somehow scope it only to installed apps

@jfdoming commented on GitHub (Mar 13, 2024): > > Just a thought on what _might_ be happening. There was a recent improvement to allow PWA support to work offline. If your authentication is failing in some way or of the PWA just can't see the server, the PWA would still work but as an offline application. Any settings that are only accessible when the server is connected wouldn't be available... which I believe includes secrets for bank sync integrations. > > hmm, although this is happening on my desktop & laptop? I believe the offline PWA support that was added works whether or not you actually install the app. Maybe we need a setting toggle to disable offline support? Or somehow scope it only to installed apps
GiteaMirror commented 2026-02-28 19:27:18 -06:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Mar 13, 2024):

@jfdoming I feel like not allowing the offline mode unless it was actually installed as an app makes sense

@youngcw commented on GitHub (Mar 13, 2024): @jfdoming I feel like not allowing the offline mode unless it was actually installed as an app makes sense
GiteaMirror commented 2026-02-28 19:27:18 -06:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Mar 13, 2024):

I guess we should also look at putting in some info in the docs on opening up just the api endpoints

@youngcw commented on GitHub (Mar 13, 2024): I guess we should also look at putting in some info in the docs on opening up just the api endpoints
GiteaMirror commented 2026-02-28 19:27:18 -06:00
Author
Owner
Copy Link

@crispybegs commented on GitHub (Mar 13, 2024):

are you leaving the web page open then coming back to it? It sounds like no, but just to be sure.

no, opening fresh each day

@crispybegs commented on GitHub (Mar 13, 2024): > are you leaving the web page open then coming back to it? It sounds like no, but just to be sure. no, opening fresh each day
GiteaMirror commented 2026-02-28 19:27:19 -06:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Mar 13, 2024):

bump: https://github.com/actualbudget/actual/issues/2456#issuecomment-1992522756

It's highly unlikely this is related to the PWA offline mode. My bet is on server misconfiguration causing the remote database to be wiped periodically. That's the only thing that might explain Actual auth tokens getting invalidated.

@MatissJanis commented on GitHub (Mar 13, 2024): bump: https://github.com/actualbudget/actual/issues/2456#issuecomment-1992522756 It's highly unlikely this is related to the PWA offline mode. My bet is on server misconfiguration causing the remote database to be wiped periodically. That's the only thing that might explain Actual auth tokens getting invalidated.
GiteaMirror commented 2026-02-28 19:27:19 -06:00
Author
Owner
Copy Link

@crispybegs commented on GitHub (Mar 13, 2024):

bump: #2456 (comment)

It's highly unlikely this is related to the PWA offline mode. My bet is on server misconfiguration causing the remote database to be wiped periodically. That's the only thing that might explain Actual auth tokens getting invalidated.

could be, but i'm not sure what the misconfiguration might be. I did a very standard docker compose installation.
my compose is

version: '3'
services:
  actual_server:
    image: docker.io/actualbudget/actual-server:latest
    ports:
      - '5006:5006'
    volumes:
      - /path/to/my/cash/actual-data:/data
    restart: unless-stopped

that's it

@crispybegs commented on GitHub (Mar 13, 2024): > bump: [#2456 (comment)](https://github.com/actualbudget/actual/issues/2456#issuecomment-1992522756) > > It's highly unlikely this is related to the PWA offline mode. My bet is on server misconfiguration causing the remote database to be wiped periodically. That's the only thing that might explain Actual auth tokens getting invalidated. could be, but i'm not sure what the misconfiguration might be. I did a very standard docker compose installation. my compose is ``` version: '3' services: actual_server: image: docker.io/actualbudget/actual-server:latest ports: - '5006:5006' volumes: - /path/to/my/cash/actual-data:/data restart: unless-stopped ``` that's it
GiteaMirror commented 2026-02-28 19:27:19 -06:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Mar 13, 2024):

Check the network logs when opening the page - if it's auth issue you will see a failed API call (403 I think). If that's the case then something interesting is happening in your server instance. Something is dropping your auth table and recreating. Which is weird.. it might also mean your transaction changes are also being deleted from the server (check this by opening an incognito tab and logging in - do you see files on the server? Do this AFTER you see the "server offline" button but BEFORE re-logging into the server from your non-incognito window).

There's two action items in here for you. Could you please do them and feed the information back to us?

@MatissJanis commented on GitHub (Mar 13, 2024): > Check the network logs when opening the page - if it's auth issue you will see a failed API call (403 I think). If that's the case then something interesting is happening in your server instance. Something is dropping your auth table and recreating. Which is weird.. it might also mean your transaction changes are also being deleted from the server (check this by opening an incognito tab and logging in - do you see files on the server? Do this AFTER you see the "server offline" button but BEFORE re-logging into the server from your non-incognito window). There's two action items in here for you. Could you please do them and feed the information back to us?
GiteaMirror commented 2026-02-28 19:27:20 -06:00
Author
Owner
Copy Link

@crispybegs commented on GitHub (Mar 13, 2024):

Check the network logs when opening the page - if it's auth issue you will see a failed API call (403 I think). If that's the case then something interesting is happening in your server instance. Something is dropping your auth table and recreating. Which is weird.. it might also mean your transaction changes are also being deleted from the server (check this by opening an incognito tab and logging in - do you see files on the server? Do this AFTER you see the "server offline" button but BEFORE re-logging into the server from your non-incognito window).

There's two action items in here for you. Could you please do them and feed the information back to us?

sorry, yes, I will, but i need to wait for it to happen again before i can do them as it's currently working fine after i logged in early this morning

@crispybegs commented on GitHub (Mar 13, 2024): > > Check the network logs when opening the page - if it's auth issue you will see a failed API call (403 I think). If that's the case then something interesting is happening in your server instance. Something is dropping your auth table and recreating. Which is weird.. it might also mean your transaction changes are also being deleted from the server (check this by opening an incognito tab and logging in - do you see files on the server? Do this AFTER you see the "server offline" button but BEFORE re-logging into the server from your non-incognito window). > > There's two action items in here for you. Could you please do them and feed the information back to us? sorry, yes, I will, but i need to wait for it to happen again before i can do them as it's currently working fine after i logged in early this morning
GiteaMirror commented 2026-02-28 19:27:20 -06:00
Author
Owner
Copy Link

@crispybegs commented on GitHub (Mar 13, 2024):

Check the network logs when opening the page - if it's auth issue you will see a failed API call (403 I think). If that's the case then something interesting is happening in your server instance. Something is dropping your auth table and recreating. Which is weird.. it might also mean your transaction changes are also being deleted from the server (check this by opening an incognito tab and logging in - do you see files on the server? Do this AFTER you see the "server offline" button but BEFORE re-logging into the server from your non-incognito window).

There's two action items in here for you. Could you please do them and feed the information back to us?

alrighty. so this just happened again.
looking at the dev console in chrome i can see this error

Access to fetch at 'https://xxxx.cloudflareaccess.com/cdn-cgi/access/login/actual.mydomain.uk?kid=56e94xxxredacted' (redirected from 'https://actual.mydomain.uk/account/validate') from origin 'https://actual.mydomain.uk' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
kcab.worker.fb549REDACTEDbd06ea0f.js:254 TypeError: Failed to fetch
    at uQ (kcab.worker.fb549REDACTEDbd06ea0f.js:130:6447)
    at bc.subscribe-get-user (kcab.worker.fb549REDACTEDbd06ea0f.js:254:5548)

and there's also this

Cookies with the SameSite=None; Secure and not Partitioned attributes that operate in cross-site contexts are third-party cookies. In future Chrome versions, setting third-party cookies will be blocked. This behavior protects user data from cross-site tracking.
Please refer to the article linked to learn more about preparing your site to avoid potential breakage.
1 cookie
Name	Domain & Path
CF_Session	mydomain.cloudflareaccess.com/

I also did your other request, logging in via an incognito window, but it was exactly the same as when I log in normally. I go through the cloudflare verification process, then log in to actual.. and everything's working but my date settings have been reverted to US formatting again (MM/DD/YYY).. so there's no difference in the experience of logging in incognito or not.

@crispybegs commented on GitHub (Mar 13, 2024): > > Check the network logs when opening the page - if it's auth issue you will see a failed API call (403 I think). If that's the case then something interesting is happening in your server instance. Something is dropping your auth table and recreating. Which is weird.. it might also mean your transaction changes are also being deleted from the server (check this by opening an incognito tab and logging in - do you see files on the server? Do this AFTER you see the "server offline" button but BEFORE re-logging into the server from your non-incognito window). > > There's two action items in here for you. Could you please do them and feed the information back to us? alrighty. so this just happened again. looking at the dev console in chrome i can see this error ``` Access to fetch at 'https://xxxx.cloudflareaccess.com/cdn-cgi/access/login/actual.mydomain.uk?kid=56e94xxxredacted' (redirected from 'https://actual.mydomain.uk/account/validate') from origin 'https://actual.mydomain.uk' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled. kcab.worker.fb549REDACTEDbd06ea0f.js:254 TypeError: Failed to fetch at uQ (kcab.worker.fb549REDACTEDbd06ea0f.js:130:6447) at bc.subscribe-get-user (kcab.worker.fb549REDACTEDbd06ea0f.js:254:5548) ``` and there's also this ``` Cookies with the SameSite=None; Secure and not Partitioned attributes that operate in cross-site contexts are third-party cookies. In future Chrome versions, setting third-party cookies will be blocked. This behavior protects user data from cross-site tracking. Please refer to the article linked to learn more about preparing your site to avoid potential breakage. 1 cookie Name Domain & Path CF_Session mydomain.cloudflareaccess.com/ ``` I also did your other request, logging in via an incognito window, but it was exactly the same as when I log in normally. I go through the cloudflare verification process, then log in to actual.. and everything's working but my date settings have been reverted to US formatting again (MM/DD/YYY).. so there's no difference in the experience of logging in incognito or not.
GiteaMirror commented 2026-02-28 19:27:20 -06:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Mar 14, 2024):

Ok, so here's what's happening:

The first request made from actual is to validate your auth token. This request then gets redirected to cloudflare because your cloudflare auth has expired. Because there are no CORS headers in cloudflare - actual is not able to read the API response. Thus it considers you to be "offline".

The first patch will be to add CORS headers to the cloudflare request so that actual could communicate with it. After that is done.. there might be other things that you would need to re-configure so the initial actual auth request is retriggered.

My recommendation would be to fix the cors headers and then see if thst makes it work. If it doesn't - please feel free to reach out to the folks on the community discord. Discord is a much better place for support.

As for not saving date format: yes, this is only stored locally. If you wipe the cache each day then also these settings get wiped.

Closing as this is not a bug report.

@MatissJanis commented on GitHub (Mar 14, 2024): Ok, so here's what's happening: The first request made from actual is to validate your auth token. This request then gets redirected to cloudflare because your cloudflare auth has expired. Because there are no CORS headers in cloudflare - actual is not able to read the API response. Thus it considers you to be "offline". The first patch will be to add CORS headers to the cloudflare request so that actual could communicate with it. After that is done.. there might be other things that you would need to re-configure so the initial actual auth request is retriggered. My recommendation would be to fix the cors headers and then see if thst makes it work. If it doesn't - please feel free to reach out to the folks on the community discord. Discord is a much better place for support. As for not saving date format: yes, this is only stored locally. If you wipe the cache each day then also these settings get wiped. Closing as this is not a bug report.
GiteaMirror commented 2026-02-28 19:27:21 -06:00
Author
Owner
Copy Link

@crispybegs commented on GitHub (Mar 14, 2024):

CORS header

aha thank you!
i found this section in the cloudflare applications for the access rules for my domain. Is it as simple as switching that on?
(sorry, i've never heard of CORS before so i have no idea if doing so is a security risk or something)

Screenshot 2024-03-14 at 08 51 18
@crispybegs commented on GitHub (Mar 14, 2024): > CORS header aha thank you! i found this section in the cloudflare applications for the access rules for my domain. Is it as simple as switching that on? (sorry, i've never heard of CORS before so i have no idea if doing so is a security risk or something) <img width="984" alt="Screenshot 2024-03-14 at 08 51 18" src="https://github.com/actualbudget/actual/assets/129169122/c3f3a126-d41c-445d-943e-70d45feef6b0">
GiteaMirror commented 2026-02-28 19:27:21 -06:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Mar 14, 2024):

If you don't have much expertise here I would advise to use one of the recommended low-tech deployment methods: pikapods or fly.

Please use the community discord if you wish to seek further assistance about cloudflare configuration. The community is quite active there.

@MatissJanis commented on GitHub (Mar 14, 2024): If you don't have much expertise here I would advise to use one of the recommended low-tech deployment methods: pikapods or fly. Please use the community discord if you wish to seek further assistance about cloudflare configuration. The community is quite active there.
GiteaMirror commented 2026-02-28 19:27:21 -06:00
Author
Owner
Copy Link

@mathisgauthey commented on GitHub (Feb 28, 2025):

CORS header

aha thank you! i found this section in the cloudflare applications for the access rules for my domain. Is it as simple as switching that on? (sorry, i've never heard of CORS before so i have no idea if doing so is a security risk or something)
Screenshot 2024-03-14 at 08 51 18

Hey there, did you end up finding a working solution ? I do struggle with that one. I'm using Cloudflare Tunnel with access configured to send me an OTP by mail. I host actual behind my nginx proxy manager which manages the SSL cert from Cloudflare.

@mathisgauthey commented on GitHub (Feb 28, 2025): > > CORS header > > aha thank you! i found this section in the cloudflare applications for the access rules for my domain. Is it as simple as switching that on? (sorry, i've never heard of CORS before so i have no idea if doing so is a security risk or something) > <img alt="Screenshot 2024-03-14 at 08 51 18" width="984" src="https://private-user-images.githubusercontent.com/129169122/312767808-c3f3a126-d41c-445d-943e-70d45feef6b0.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NDA3NDMwMDUsIm5iZiI6MTc0MDc0MjcwNSwicGF0aCI6Ii8xMjkxNjkxMjIvMzEyNzY3ODA4LWMzZjNhMTI2LWQ0MWMtNDQ1ZC05NDNlLTcwZDQ1ZmVlZjZiMC5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwMjI4JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDIyOFQxMTM4MjVaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1iOGQyNGJiMzkxODNhMTljOWRkOTFmNWI2NmIzYWI4ODA3OWJhMTJhNDg4OGQ4Nzc3MTQ1ZGM5ODBlMDQ3YTUwJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.L0dHmhyx6ZaEQZZBc6HYT6j_6xrOx9k3A1-GAdqxn5s"> Hey there, did you end up finding a working solution ? I do struggle with that one. I'm using Cloudflare Tunnel with access configured to send me an OTP by mail. I host actual behind my nginx proxy manager which manages the SSL cert from Cloudflare.
GiteaMirror commented 2026-02-28 19:27:22 -06:00
Author
Owner
Copy Link

@crispybegs commented on GitHub (Feb 28, 2025):

Hey there, did you end up finding a working solution ? I do struggle with that one. I'm using Cloudflare Tunnel with access configured to send me an OTP by mail. I host actual behind my nginx proxy manager which manages the SSL cert from Cloudflare.>

I'm afraid not, i just live with the cookie clearing

@crispybegs commented on GitHub (Feb 28, 2025): > Hey there, did you end up finding a working solution ? I do struggle with that one. I'm using Cloudflare Tunnel with access configured to send me an OTP by mail. I host actual behind my nginx proxy manager which manages the SSL cert from Cloudflare.> I'm afraid not, i just live with the cookie clearing
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#983
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?