Skip to content
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

After changing wifi networks, exporter doesn't work anymore[BUG] #356

Open
Hendrxxx666 opened this issue Jan 8, 2021 · 14 comments
Open

Comments

@Hendrxxx666
Copy link

Hi,

I've been using SWEX for a while now, sometimes when i'm at work but since we switched offices (and thus, wifi networks), i seem to have been unable to export my JSON file. I still use the same desktop with SWEX on it, firewall allows SWEX, the IP/port is correct but everytime i start the proxy and then load up the SW app, the screen stays black for a while and then says "Failed to connect with the network. Please try again later.". Do you have any experience with this and/or a fix?

Thanks in advance

@Xzandro
Copy link
Owner

Xzandro commented Jan 11, 2021

Sadly I dont have any experience with this and I pretty much only haver one Wifi network. So if someone else wants to look into that I wouldn't mind.

@HamzaLodhi

This comment has been minimized.

@Xzandro

This comment has been minimized.

@Celteron

This comment has been minimized.

@Xzandro
Copy link
Owner

Xzandro commented Jan 19, 2021

You are not. Please don't use this issue for help regarding the new (old) HTTPS steps or I will lock this issue.

@deirdresm

This comment has been minimized.

@deirdresm

This comment has been minimized.

@Xzandro
Copy link
Owner

Xzandro commented Jan 22, 2021

This is also not relevant to this issue. Its because of com2us's reactivation of HTTPS, as described in the countless closed issues here. See #359 Really thinking about locking this issue for now, so people don't derail / confuse this with the HTTPS issue and not understanding that they need additional steps again now.

This might a valid real issue or bug, but this has nothing to do with the current HTTPS situation.

@deirdresm
Copy link

Apologies for the noise then, and thank you.

Perhaps a small line on the top of the README would help avoid more dups?

@Xzandro
Copy link
Owner

Xzandro commented Jan 22, 2021

Perhaps. When I look at most of these issues, I kinda doubt that people would actually read this first tho. :/

@deirdresm

This comment has been minimized.

@Xzandro

This comment has been minimized.

@nessoaf

This comment has been minimized.

@Xzandro
Copy link
Owner

Xzandro commented Jan 22, 2021

Okay, will lock this issue now. At this point this is just a dumpster fire of an issue for people, who don't udnerstand that they need a additional steps because of HTTPS, See #359

Might reopen in a few weeks.

Repository owner locked and limited conversation to collaborators Jan 22, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants