What Are You Doing Right Now
-
@thwr said in What Are You Doing Right Now:
Submitted two little issues and three feature request in the UBNT forums about 8 hours ago. Four of them already accepted. I really like them.
What did you submit?
-
@dustinb3403 said in What Are You Doing Right Now:
@thwr said in What Are You Doing Right Now:
Submitted two little issues and three feature request in the UBNT forums about 8 hours ago. Four of them already accepted. I really like them.
What did you submit?
Just a few little things: VLAN, MSTP and certificate deployment via UNMS, maintenance mode for ES/ER (e.g. prep a switch, put it in the shelve for later -> site offline, switch -> outage) and another bugger: Whenever you click a link for an ES in UNMS that only speaks HTTPS (what I prefer), the link is only HTTP.
Last thing was about factory default firmware, which doesn't allow you to add them to UNMS out of the box. You need to upload 1.7.3 first.
You could vote for those features here: https://community.ubnt.com/t5/UNMS-Feature-Requests/idb-p/UNMSFeatureRequests/tab/most-recent (or search for 'thwr')
-
@dafyre said in What Are You Doing Right Now:
@dustinb3403 said in What Are You Doing Right Now:
@dafyre said in What Are You Doing Right Now:
@dustinb3403 said in What Are You Doing Right Now:
Did anyone else know that UrBackup has CBT for only $17/system. . . my god that is cheap. .
I haven't tried URBackup in a long time. Do you use it?
We may as we're doing some transitional setup and may need something as an interim solution. And for only $17 I can save a lot of time and headache with the questions "why is it going so slowly". . .
I'd be interested in hearing your experience with it. I used it in the past and it did work for file recovery (never had to recover a full system with it).
This is still in the early discussion phase, not sure if we will even need it or not. But for $17 I might just purchase a license to test.
-
@thwr said in What Are You Doing Right Now:
Last thing was about factory default firmware, which doesn't allow you to add them to UNMS out of the box. You need to upload 1.7.3 first.
This is not a new thing. The EdgeRouters still ship with version 1.2 i think.
They have never updated production on any Edge hardware that I know of.
-
Playing with NGINX and got my first reverse proxy working sending http://wordpress.mydomain.co.uk that points to the NGINX ip show my wordpress site
Now to try and get it to work with https - On that note
Do i need to get the wordpress server configured for SSL (https:) or is that handled by NGINX? -
@jaredbusch said in What Are You Doing Right Now:
@thwr said in What Are You Doing Right Now:
Last thing was about factory default firmware, which doesn't allow you to add them to UNMS out of the box. You need to upload 1.7.3 first.
This is not a new thing. The EdgeRouters still ship with version 1.2 i think.
They have never updated production on any Edge hardware that I know of.
Yep, sadly
-
@hobbit666 said in What Are You Doing Right Now:
Playing with NGINX and got my first reverse proxy working sending http://wordpress.mydomain.co.uk that points to the NGINX ip show my wordpress site
Now to try and get it to work with https - On that note
Do i need to get the wordpress server configured for SSL (https:) or is that handled by NGINX?Depends. You basically want the connection between your proxy and your webserver to be encrypted too. There are a few cases where you may omit that, for example if you trust your host and both systems run on the same metal.
Basically, the same reasons that make you use HTTPS on LANs apply here too, IMHO.
-
@thwr said in What Are You Doing Right Now:
@hobbit666 said in What Are You Doing Right Now:
Playing with NGINX and got my first reverse proxy working sending http://wordpress.mydomain.co.uk that points to the NGINX ip show my wordpress site
Now to try and get it to work with https - On that note
Do i need to get the wordpress server configured for SSL (https:) or is that handled by NGINX?Depends. You basically want the connection between your proxy and your webserver to be encrypted too. There are a few cases where you may omit that, for example if you trust your host and both systems run on the same metal.
Basically, the same reasons that make you use HTTPS on LANs apply here too, IMHO.
Another option is to set the firewall to only allow the proxy access to WordPress.
-
@thwr What i thought, job for tomorrow move my test Wordpress site to HTTPS
-
D&D night.
-
Just got home to Dallas and unpacked the car. What a long day it was. The wind was SO awful. I'm worn out.
-
@dustinb3403 said in What Are You Doing Right Now:
Did anyone else know that UrBackup has CBT for only $17/system. . . my god that is cheap. .
I had no idea.
-
@black3dynamite said in What Are You Doing Right Now:
@thwr said in What Are You Doing Right Now:
@hobbit666 said in What Are You Doing Right Now:
Playing with NGINX and got my first reverse proxy working sending http://wordpress.mydomain.co.uk that points to the NGINX ip show my wordpress site
Now to try and get it to work with https - On that note
Do i need to get the wordpress server configured for SSL (https:) or is that handled by NGINX?Depends. You basically want the connection between your proxy and your webserver to be encrypted too. There are a few cases where you may omit that, for example if you trust your host and both systems run on the same metal.
Basically, the same reasons that make you use HTTPS on LANs apply here too, IMHO.
Another option is to set the firewall to only allow the proxy access to WordPress.
That's the more standard approach. Less overhead.
-
Just made dinner for both of the kids and got their Steam system set up, so they are video gaming now.
-
Finishing NGNIX Proxy project
-
Just got the kids off to bed.
-
Finished other projects with Lambda, now to bed.
-
Chatting with a sick friend in Transylvania.
-
Just moved our core switches and routers 2 racks to the left.
-
@thwr said in What Are You Doing Right Now:
Just moved our core switches and routers 2 racks to the left.
All kinds of excitement going on there.