I am trying to add an SSL certificate to my router so that I can access the router securely, and not worry about any browser warnings. Although I only access the router directly via ethernet, I would still like that extra bit of security. I'm also trying to learn.
I attempted to do this using the openwrt documentation here and elsewhere. I came across some issues. In step 7, it says go to LuCI > Services. There is no Services in my interface. I checked everywhere and couldn't find it. I am using the GL-iNet GL750 "Mudi". OpenWrt version 19.07.8.
Is there a way to complete the steps in the terminal, not in the interface?
I figured I was using the latest version. I keep the router updated via the main gl-inet interface. Is there any reason why it's not updating?
installed the luci package mentioned on the wiki page you linked to ?
Yes, I followed all instructions leading up to step 7.
Also, for some reason I can no longer access the router in my browser. I can ssh into it, but not access the interface in the browser. I must've screwed up somewhere.
It appears you are using firmware that is not from the official OpenWrt project.
When using forks/offshoots/vendor-specific builds that are "based on OpenWrt", there may be many differences compared to the official versions (hosted by OpenWrt.org). Some of these customizations may fundamentally change the way that OpenWrt works. You might need help from people with specific/specialized knowledge about the firmware you are using, so it is possible that advice you get here may not be useful.
Ask for help from the maintainer(s) or user community of the specific firmware that you are using.
Provide the source code for the firmware so that users on this forum can understand how your firmware works (OpenWrt forum users are volunteers, so somebody might look at the code if they have time and are interested in your issue).
If you believe that this specific issue is common to generic/official OpenWrt and/or the maintainers of your build have indicated as such, please feel free to clarify.
So even though I am using openwrt, I can't get support with my version because I'm using the version that came with the router, which is supposedly not really openwrt? And you're suggesting gl-inet is falsely advertising that it ships with openwrt?
My intuition on this is that I should keep using the gl-inet version, because its actually designed to work on the hardware. I have a feeling if I rip out the software and replace it with the "official" version, I may not be able to use some of the features. The LuCI is an extended featureset that I only use if I need to do advanced things, the majority of my configuration occurs in the gl-inet interface. Does LuCI provide the same features, such as checking SMS messages?
I really just came here to solve one problem, which already took me down a rabbit hole, I don't really care to go down another one.
Frankly, if I don't get help here I'm just going to go somewhere else (I'm already looking for help on the gl-inet forum). And they may not have speciality knowledge on openwrt. I don't feel comfortable replacing the software because I doubt it won't cause problems, and in my honest opinion, I don't think gl-inet are untrustworthy as they have some of the best routers available with a large customer base. I don't know all the rules about open source software but if you're not allowed to use openwrt in your products without some permission then it's probably not completely open source. Then again, I could be wrong.
Can I get help on my problem or should I go somewhere else?
Apologies for being blunt, but the vendor-specific version is their software. If they don't have knowledge about what they have put on their routers then that's not our issue. And we certainly don't have any knowledge of what changes they've made and how they may interact with what they haven't altered.
If you want assistance with gl-inet's software then you need to get it from them. We can't assist with other vendors' software.
I don't know about that firmware but it probably isn't so different that you couldn't install your own certificate by copying the files with the CLI. First examine /etc/config/uhttpd to find where the server's cert and key are stored, then replace those files with your own.