Firefly III
Importer fails when using Docker implementation on non-standard port #9414
Unanswered
ll3N1GmAll
asked this question in
Q&A
Replies: 1 comment 1 reply
-
|
Which reverse proxy is in front of the importer? |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
All I have is the docker deployment with the 4 docker images that come down as a part of that setup. I do not have any additional reverse proxy in front of it. I get this odd behavior even when accessing the importer directly from a browser on the server, connecting via 127.0.0.1:81. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Importer fails when using Docker implementation on non-standard port.
I tried navigating to the importer on port 81 from a remote PC (accessing via IP) and locally via localhost and 127.0.0.1. Importer operations try to navigate to URLs on localhost even when using this from a remote PC. This seems like a bug since I am logged in to 192.168.x.x and the Importer operation shows it is trying to go to "localhost" in the URL after clicking "submit".
Also, importer operations try going to port 80 in the URL field even though firefly is running successfully on a non standard port.
Beta Was this translation helpful? Give feedback.
All reactions