@AliAS remember after locating and fixing the error to hit ctrl + o to save and ctrl + x to exit nano.

Thanks to both of you for the quick replys. As I said, I’m very new but learning quickly. After seeing Mykel’s post (sorry if I’m spelling that incorrectly as I cannot see the post while typing a reply on my android) I reopened the custom.css file and noticed I made a syntax error. I replaced the colon after yellow with a semicolon and I was good to go.

Another suggestion, and someone please correct me if I am wrong, you could delete the config.js file and save as or copy the config-sample.js as a new config.js file. That way you have a functioning config.js. But doing so, you would have to reconfigure all your modules. Does that sound right?

@cruunnerr I have just encountered the same error, MM loads on my display BUT i cannot connect to remote-control from a browser. Running stock modules - weather + wunderground, remote-control, remote-control-repository and iFrameReload. Remote access worked fine yesterday before installing iFrame last night. Gonna do some troubleshooting.

@doubleT That worked perfect. Thanks again!

I see. I’ll give it a try. Thank you very much.

Does anybody know how to use a line break within a compliment? I’ve tried about a dozen different ways to no avail.

External join file? Lol, thats way outta my league.

@sek_is_back add it into your custom.css file. It is referred to as

.MMM-WunderGround .tableheader

You can change
font-size:
and
color:

Sorry I don’t know how to post the code for you.

@maestro82 The top row is .MMM-WunderGround .pop
This will also affect the row pertaining to rain chance percentage. I’m trying to find a way to address them separately if anyone knows how.

Another suggestion, and someone please correct me if I am wrong, you could delete the config.js file and save as or copy the config-sample.js as a new config.js file. That way you have a functioning config.js. But doing so, you would have to reconfigure all your modules. Does that sound right?

@AliAS remember after locating and fixing the error to hit ctrl + o to save and ctrl + x to exit nano.

I had a similar problem. It showed an error for my entire addition to the config.js. Run check:config again and pay close attention to the beginning of the output. The first error should say something about expecting a bracket of one kind and it was returned a bracket of a different kind. It will also tell you the line of the error. Now nano back into config scroll down to your addition and press ctrl + c. The bottom of your screen should give you your current line number. Find the error. Mine was a missing bracket. Fixing this error fixed the entire script. All other errors were the result of the first. Sorry if I wasn’t clear or missed something, im still a new to this too. Hope it helps.