UNSOLVED Google Search

[marvnfl]

This may or may not be NodeBB related.

Google Search works fine, but if you type domain.com into the address bar of Google Chrome with trailing text, e.g., "domain.com test" directs to NodeBB's search plugin. The problem is that it's using domain.com:4567 (with the port).

All domain.com and domain.net traffic is redirected to https://domain.com using nginx.

Is Google, nginx, or NodeBB affixing the port to the URL?

[PitaJ]

yeah make sure the url in config.json doesn't include the port and then set the port separately

"url": "https://domain.com",
"port": "4567",

[marvnfl]

@PitaJ The URL was already set to "https://domain.com," but I did not specify the port. I specified the port and no change.

[julian]

You'll want to ensure that the port is removed from config.json.

[marvnfl]

@julian My config.json looks like this currently:

"url": "https://domain.com",
"port": "4567",

but before @PitaJ's recommendation it looked like:

"url": "https://domain.com",

[julian]

@marvnfl If you inspect the source of the page, you'll see this line

<link rel="search" type="application/opensearchdescription+xml" href="/osd.xml" />

Follow the link, and let us know what the content reads.

[marvnfl]

@julian Here you are:

<OpenSearchDescription xmlns="http://a9.com/-/spec/opensearch/1.1/">
<ShortName>[redacted]</ShortName>
<Description/>
<Url type="text/html" method="get" template="https://domain.com/search?term={searchTerms}&in=titlesposts"/>
</OpenSearchDescription>

Seems right?

[PitaJ]

@marvnfl yeah seems right. Have you tried with a different browser? Maybe it's cached.

[julian]

Yeah, am thinking it was set incorrectly before, and it'll just be awhile for chrome to update. Not sure how to clear that part