Skip to content

[Bug] website assets not loading and search engine for proxy not working #1059

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

Open
ihatevoicemod opened this issue Apr 29, 2025 · 3 comments
Assignees
Labels
Bug Report Tell us about an issue you are having using the site.

Comments

@ihatevoicemod
Copy link

ihatevoicemod commented Apr 29, 2025

Describe the bug
whenever i start up the code space and enter the website it doesn't load and when it does a lot of assets and background pictures are missing it also sometimes never loads and i try to refresh the website and it never fixes it and it does not load any website.

To Reproduce
Steps to reproduce the behavior:

  1. open the codespace in a fork and set it up
  2. try to load the proxy
  3. see what happens

Expected behavior
A clear and concise description of what you expected to happen.
me being able to use the proxy to go on websites without being blocked by assets not working and the search engine not working
Screenshots
If applicable, add screenshots to help explain your problem.

Image

Image

Image

Image

Image

Device Information (please complete the following information):

  • Device: Chromebook
  • OS ChromeOS
  • Browser Chrome

Additional context
Add any other context about the problem here.

Important

Do not post your personal information here this includes but is not limited to email addresses, names, and age.

@ihatevoicemod ihatevoicemod added the Bug Report Tell us about an issue you are having using the site. label Apr 29, 2025
@ihatevoicemod ihatevoicemod changed the title [Bug] [Bug] website assets not loading and search engine for proxy not working Apr 29, 2025
@Gitinsideofthehubcoder
Copy link

Gitinsideofthehubcoder commented May 6, 2025

Most likely you did not set the port visibility to public.

There may be restrictions set by your Wifi network or on the device itself. Are you using a Linux?

@ihatevoicemod
Copy link
Author

Most likely you did not set the port visibility to public.

There may be restrictions set by your Wifi network or on the device itself. Are you using a Linux?

i did set it to public thats the problem

@ihatevoicemod
Copy link
Author

and no im using chromebook

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Report Tell us about an issue you are having using the site.
Projects
None yet
Development

No branches or pull requests

3 participants