TypeError: failed to fetch #2
MotorTruck1221 opened this issue · comments
Issue tracker is ONLY used for reporting bugs. New features should be discussed on our Discord server.
I know this is an issue that has already been opened. This is more detailed, however
Expected Behavior
- When going to any website (e.x: https://github.com) it should show the website that the user has requested
Current Behavior
- When I Type in a url it throws an error of:
TypeError: failed to fetch
pictures below in order (Ungoogle Chromium v106)
Possible Solution
- I believe this is more related to the Ultraviolet Static Repository as one version ago this was working fine.
Steps to Reproduce
- Setup the newest version of Ultraviolet-Node
- Type in (or search) what ever you wish
- See a
TypeError: failed to fetch
Context (Environment)
- Host: Hosted on Digital ocean VPS.
- OS: Ubuntu 20.04 (LTS)
- My setup: NGINX Proxy Manager --> Ultraviolet
- Node JS version: 18
- NPM version 8
- I am passing all correct headers:
location / {
# Upgrade WebSockets
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'Upgrade';
# Increase header buffer
proxy_connect_timeout 10;
proxy_send_timeout 90;
proxy_read_timeout 90;
proxy_buffer_size 128k;
proxy_buffers 4 256k;
proxy_busy_buffers_size 256k;
proxy_temp_file_write_size 256k;
proxy_pass http://10.124.0.3:1042; # change this to the port UltraViolet is listening on
# The small block below will block googlebot
if ($http_user_agent ~ (Googlebot)) {
return 403;
}
}
(See Proxdocs)
- Tried on three different browsers:
- Firefox v105.0.2
- Ungoogled Chromium v106.0.5249.9
- Chrome v106.0.5249.91
- I am trying to update my UltraViolet instance hosted on my VPS and it will break if I do.
- I am a developer for a non-official proxy called Weeb Central and updating the website will break it
- I am developing my own proxy (not public on GH yet) and updating will break the website from working
Possible Implementation
I don't know a possible fix however I hope this is detailed enough that it will help it get fixed sooner.
A cause of this error may be due to problems with the underlying Bare Server.
Here are steps to debug this problem:
- Go to the Ultraviolet-Node homepage
- Open Devtools
- Go to the network tab
- Enable "Persist Logs"
- Produce your problem
- Look for a request to
/bare/v1/
, what's the status code?
Can you provide a screenshot of /bare/
?
This also happens to me, not sure how to fix it. This wasn't doing this previously, and I hadn't updated the app at all.
same issue here, however spamming the reload button partially fixes it with https://incog.dev/bare/v1/ responding with "MISSING_BARE_HEADER"
nodejs v18 & npm 8
Ah. Not only are we using an external Bare server by default (this was a mistake...) but incog.dev's bare server has fallen. Every other request on my end goes through. This will be addressed shortly.
This should be fixed. Redeploy your instance.
@MemeGiver Try clearing your site data. This will refresh the UV config.
@MemeGiver Try clearing your site data. This will refresh the UV config.
working now, thanks a lot