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 logging in, assets flash then completely blank screen #15

Closed
jiznon opened this issue Aug 29, 2020 · 12 comments
Closed

After logging in, assets flash then completely blank screen #15

jiznon opened this issue Aug 29, 2020 · 12 comments

Comments

@jiznon
Copy link

jiznon commented Aug 29, 2020

I was able to clone git and point qB to the /release folder. I visited the webui and it loaded the iQbit webui homepage. After inputting credentials and clicking sign in, the screen is blank. If I disable "Use alternative Web UI" in qB and refresh my browser, I'm able to see the default UI as if I'm logged in.

Ubuntu 18.04.4 LTS VM
qBittorrent 4.2.5 -- currently have 55 torrents active

Visiting webui from within Firefox on said VM, as well as from Chrome browser from Windows 10 host, and Chrome on iOS, results in same behavior.

Screenshot is of the assets that load for a second or two before going completely blank. Favicon and "iQbit" header stay.:

iqbitissue

Would love to use this!

@ntoporcov
Copy link
Owner

This sounds like a JS error on something im doing.

Can you check the console to see if it's showing any errors?

@jiznon
Copy link
Author

jiznon commented Sep 9, 2020

Sure thing! From Chrome:

46react-dom.production.min.js:209 TypeError: Cannot read property 'short' of undefined
at F (TorrentBox.js:140)
at Yr (react-dom.production.min.js:153)
at gs (react-dom.production.min.js:261)
at cl (react-dom.production.min.js:246)
at sl (react-dom.production.min.js:246)
at Js (react-dom.production.min.js:239)
at react-dom.production.min.js:123
at e.unstable_runWithPriority (scheduler.production.min.js:19)
at Uo (react-dom.production.min.js:122)
at qo (react-dom.production.min.js:123)
ts @ react-dom.production.min.js:209
TorrentBox.js:140 Uncaught (in promise) TypeError: Cannot read property 'short' of undefined
at F (TorrentBox.js:140)
at Yr (react-dom.production.min.js:153)
at gs (react-dom.production.min.js:261)
at cl (react-dom.production.min.js:246)
at sl (react-dom.production.min.js:246)
at Js (react-dom.production.min.js:239)
at react-dom.production.min.js:123
at e.unstable_runWithPriority (scheduler.production.min.js:19)
at Uo (react-dom.production.min.js:122)
at qo (react-dom.production.min.js:123)

Update on my setup for what it matters: Created new Ubuntu 20.04 LTS VM and migrated my qBittorrent config and data. Fresh clone of iQbit.

@ntoporcov
Copy link
Owner

Did this get fixed at all?

@ntoporcov ntoporcov reopened this Jul 22, 2021
@ntoporcov
Copy link
Owner

Sorry closed by accident

@jiznon
Copy link
Author

jiznon commented Jul 22, 2021

It has not. Tested this week.

@ntoporcov
Copy link
Owner

Can you pull from the testing branch and see if it happens there too?

@ntoporcov
Copy link
Owner

I also pushed a branch called jiznon-test where I removed the mention of .short to test and see if that was actually the problem

@jiznon
Copy link
Author

jiznon commented Jul 23, 2021

Same behavior with both Testing and jiznon-test, unfortunately.

Appreciate the effort!

@ntoporcov
Copy link
Owner

Alright, one more question. Can you check the address that the network requests are going to? Does it match the address that default webui uses? I'm thinking maybe the way I'm getting the API address is not working with your setup somehow

@jiznon
Copy link
Author

jiznon commented Jul 23, 2021

Is this what you're looking for?

image

Pasting it was a huge wall of text due to expanded text copied as well. Let me know if you'd like the whole thing and I can pastebin it (or whatever you recommend).

I thought the port might be an issue so I changed it to 8080 and tested on host machine via localhost:8080 but resulted in same behavior.

@sashareds
Copy link

@jiznon I wonder if you had a similar issue to me. Mine was solved by readding a glitchy torrent. #30

@jiznon
Copy link
Author

jiznon commented Jan 28, 2022

@jiznon I wonder if you had a similar issue to me. Mine was solved by readding a glitchy torrent. #30

Wow, that was it! I removed two torrents -- one that never started downloading, and another that has been stuck at 99.7% for ages, and I can now use iQbit!

Solved! Thanks so much!

@jiznon jiznon closed this as completed Jan 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants