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

Playground seems to be 404 #147

Open
Zireael07 opened this issue Aug 7, 2023 · 1 comment
Open

Playground seems to be 404 #147

Zireael07 opened this issue Aug 7, 2023 · 1 comment

Comments

@Zireael07
Copy link

Describe the bug
At least http://nodeefficientnet.ml/ is 404

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: [e.g. iOS]
  • Browser [e.g. chrome, safari]
  • Version [e.g. 22]

Smartphone (please complete the following information):

  • Device: [e.g. iPhone6]
  • OS: [e.g. iOS8.1]
  • Browser [e.g. stock browser, safari]
  • Version [e.g. 22]

Additional context
Add any other context about the problem here.

@shwetd19
Copy link

Hey there 👋,

It's a straightforward issue that needs fixing to ensure users can access the site without running into a dead end, I'd love to dive in and help resolve this.

From what I understand, the main goal is to fix the broken link leading to a 404 error. This might involve checking the DNS records, verifying the domain configuration, or ensuring the server is properly set up to serve the site.

A potential fix could be to verify the domain's DNS settings and ensure they point to the correct server hosting the Node EfficientNet playground. Additionally, checking the server configuration to ensure it's set up to serve the site correctly would be crucial.

Would it be possible to let me tackle this? I'm excited to contribute and help to address this issue, making the site accessible again.

Cheers,
@shwetd19

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

2 participants