• Home
  • Categories
  • Recent
  • Popular
  • Top
  • Tags
  • Users
  • Groups
  • Documentation
    • Home
    • Read API
    • Write API
    • Plugin Development
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
v3.5.2 Latest
Buy Hosting

Using domain name to visit website for error reporting

Scheduled Pinned Locked Moved Technical Support
14 Posts 4 Posters 2.1k Views
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • JenklerJ Offline
    JenklerJ Offline
    Mikael Jenkler Swedes
    wrote on last edited by
    #5

    Nice, problem solved then 😉

    9 1 Reply Last reply
    0
  • julianJ Offline
    julianJ Offline
    julian GNU/Linux
    wrote on last edited by
    #6

    Likely config.url is not set properly.

    9 1 Reply Last reply
    0
  • 9 Offline
    9 Offline
    9652301
    replied to julian on last edited by 9652301
    #7

    @julian This config.url is not in the config.json? In addition, I checked the site with the console of the Chrome browser and found a lot of socket.io errors (403 errors)
    In addition, how to configure socket.io in the config.json file?

    1 Reply Last reply
    0
  • 9 Offline
    9 Offline
    9652301
    replied to Mikael Jenkler on last edited by
    #8

    @jenkler My problem hasn't been solved yet.

    1 Reply Last reply
    0
  • yariplusY Offline
    yariplusY Offline
    yariplus Community Rep
    wrote on last edited by
    #9

    Your config.json needs to have your domain in the url:

    {
        "url": "https://www.yourdomain.com",
        ....
    }
    
    9 1 Reply Last reply
    1
  • 9 Offline
    9 Offline
    9652301
    replied to yariplus on last edited by
    #10

    @yariplus I've changed what you're saying, but there are a lot of socket.io errors found in the console.

    1 Reply Last reply
    0
  • julianJ Offline
    julianJ Offline
    julian GNU/Linux
    wrote on last edited by
    #11

    Did you restart NodeBB after changing config.json?

    9 1 Reply Last reply
    0
  • 9 Offline
    9 Offline
    9652301
    replied to julian on last edited by
    #12

    @julian Now through the domain name access is not wrong, but through the IP access will appear before the error, how should this deal with?

    julianJ 1 Reply Last reply
    0
  • julianJ Offline
    julianJ Offline
    julian GNU/Linux
    replied to 9652301 on last edited by
    #13

    @9652301 In your reverse proxy's config, direct IP address access should be prohibited. Instead, catch those requests and redirect them to the proper hostname.

    9 1 Reply Last reply
    0
  • 9 Offline
    9 Offline
    9652301
    replied to julian on last edited by
    #14

    @julian I've solved the problem. Thank you very much!

    1 Reply Last reply
    1

Copyright © 2023 NodeBB | Contributors
  • Login

  • Don't have an account? Register

  • Login or register to search.
Powered by NodeBB Contributors
  • First post
    Last post
0
  • Home
  • Categories
  • Recent
  • Popular
  • Top
  • Tags
  • Users
  • Groups
  • Documentation
    • Home
    • Read API
    • Write API
    • Plugin Development