-
Notifications
You must be signed in to change notification settings - Fork 200
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Stream Proxies are lost when process restarts #320
Comments
Cannot reproduce on local instance (without docker). I tried to recreate the above bug with the following steps
@PassiveLemon could you try to see if this issue is only related to the docker build of Zoraxy? |
I am also unable to recreate this issue. I setup a TCP proxy to forward :6754 to localhost:8005 (my Zoraxy dashboard) and I am still able to access the dashboard over :6754 after restarting the container a few times. |
Confirm. Have the same problem - Zoraxy does not save stream proxy forwarding rules. Reproduced several times.
Just now after reboot Zoraxy deny access from other hosts on my network.
Have to stop all containers and ssh and zoraxy itself and restart them all.
Didn't help. Installation is totally screwed. Redeployed OS to my SBC. Almost forgot - SSH access to my SBC is not related to the issue. That was my Windows 11 host problem. |
I can curl zoraxy web-server locally though. |
Can confirm it What I also notice is that my connections generally don't work. |
I have Zoraxy installed to /opt without docker.
Immediately after restarting it with |
Since it appears that it happens on both Docker and native installs of Zoraxy, it's most likely from Zoraxy itself, I can't really help much. |
I installed Zoraxy yesterday, so it is a new install without updates |
Hello. |
Confirm the same problem with 3.1.1 Arm64 version. |
Hello, I can confirm that streams vanish after restart. This is not a docker problem. I installed zoraxy natively on ubuntu. Streams are even not backed up. I used the backup and restore function to migrate from docker to native. All other was restored except the streams. Greetings. |
Well I cannot reproduce the bug so there isn't much I can do. But I do see there are some places where the implementation can be optimized. As the added commit above, I have tried to update some stuffs in the development build and moved the stream proxy config store from database based to file based. If anyone is interested, feel free to try build it yourself to see if the problem is fixed. |
Hello. |
@ViperOGrind that sounds like a Linux user permission issue to me. You sure Zoraxy (and its folder) got the correct permission for read write? Besides, when using dev branch, you have to download and include the |
Hello. |
Yes, if you build with the development mode flag set to true in main.go, you will need to place the web folder in the same directory (cwd) as the executable. Alternatively, you can modify the development mode flag in main.go to false prior to building the dev branch to use the internal web resource (then no need the external web folder) |
Ok, I will have a look into this tonight.
That is dev mode for users (aka no-cache headers for serving upstreams), not the dev mode for Zoraxy code base. |
Ok I have tested this function again in the new v3.1.2 branch with a fresh installation. I don't see there are any issues regarding this happening. I guess this should be fixed. I will keep this open for another week after the release and if there are still issues, please let me know with additional information on how to reproduce it. |
Hello. |
Describe the bug
I have set up multiple stream proxies. When I restart the Zoraxy process, all of them are gone and I have to re-setup them. It's not a cosmetic issue, they stop working.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I expected the settings to not vanish upon restarting the process.
Screenshots
Browser (if it is a bug appears on the UI section of the system):
Host Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: