Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
  1. Home
  2. Software
  3. Multi-System Reactor
  4. sunset/sunrise question in 22251
UI not loading after upgrading to 26318
tunnusT
Sorry for a hasty post, will update some details later, but the scenario is that I managed to type a wrong password for too many times and had the following users.yaml section: authtrack: max_attempts: 4 within_minutes: 180 # 180 minutes = 3 hrs block_expiration_minutes: 10080 # 7 days At this time I used build 26298. Then noticed there's a new build with a bypass blocking feature (and yes, it said it won't remove existing block). Anyway, went ahead and upgraded to 26318, but the problem now is that UI is not loading at all (page does not answer). This also means that I cannot use "http://reactor_host:port/diag/clear_authtrack?askauth" command to clear the block (or use any other source IP for login). Docker container stays up & running and does not exit. I'll try to dig up some logs, but anything that I could immediately try out (could I delete a particular file for example)? EDIT: some logs [latest-26318]2026-11-17T20:42:32.337Z <Rule:INFO> MSR startup (rule-lculfnhm in Miscellaneous) started [latest-26318]2026-11-17T20:42:32.343Z <httpapi:NOTICE> httpapi#1 HTTP server listening on :::8111 [latest-26318]2026-11-17T20:42:32.347Z <httpapi:INFO> httpapi#1 local docs found in /opt/reactor/docs/html; setting up static service [latest-26318]2026-11-17T20:42:32.354Z <app:NOTICE> Starting WSAPI... [latest-26318]2026-11-17T20:42:32.355Z <wsapi:NOTICE> wsapi: starting version 26298 protocol [latest-26318]2026-11-17T20:42:32.523Z <Engine:INFO> Engine#1 master timer tick, local time "17/11/2026 22:42:32" (TZ offset 120 mins from UTC) [latest-26318]2026-11-17T20:42:32.542Z <Engine:NOTICE> Starting reaction MSR startup<SET> (rule-lculfnhm:S) [latest-26318]2026-11-17T20:42:32.545Z <Notifier:null> Module Notifier v26186 [latest-26318]2026-11-17T20:42:32.545Z <Engine:INFO> MSR startup<SET> all actions completed. [latest-26318]2026-11-17T20:42:32.557Z <Rule:INFO> Rule#rule-lculfnhm reaction rule-lculfnhm:S completed [latest-26318]2026-11-17T20:42:32.558Z <default:null> Module NotifyTelegram v26177
Multi-System Reactor
[Resolved] Hubitat upgrade 2.5.3.123 may have broken login
3
Topic thumbnail image
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here. Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
Multi-System Reactor
Reactor Inspect - a small read-only helper panel for MSR
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Reverse proxy & API ACL
tunnusT
I'm trying to allow anonymous access from a local network to /api/v1/log, but the problem now with the reverse proxy configuration is that this access is open via proxy to the internet. At least I wasn't able to configure ACL so that only an access from a local network would be permitted. reactor.yaml: baseurl: "http://192.168.1.12:8111" proxy_baseurl: "https://external.com:30000" trusted_proxy: "192.168.1.12" Local traffic would originate from 192.168.1.0/24 network. Synology is acting as a reverse proxy and hosting MSR as a docker container (which has its own network and IP 172.18.0.5). MSR build is latest-26298-fbb75fb8 users.yaml: - url: "/api/v1/log" method: "GET" source_ip: 172.18.0.0/24 allow: true Using the above ACL works, but it enables access via proxy also. If I use source_ip: 192.168.1.0/24, then it doesn't work either locally or remotely. So I'm kinda lost what should I use as source_ip in this case?
Multi-System Reactor
MFA
T
Topic thumbnail image
Multi-System Reactor
Grouped devices
G
I've seen many of you using Dynamic Group Controller. I'm using it myself for monitoring device battery levels. I've read and re-read the Dynamic Group Controller docs and still cannot come to an answer for my question so let me paint my scenario: I've migrated from EchoSpeaks in Hubitat ('cause borked and seemingly unmaintained) to Alexa Devices in Home Assistant ('cause not borked in 2026.11.0) to be able to send TTS to my Echo devices. In EchoSpeaks I could create groups. Sweet. In Alexa Devices I don't seem to be able to do so. As such, my thought was "wait - isn't there a way in MSR?" Is this an effective scenario that Dynamic Group Controller can be used for?
Multi-System Reactor
Login protections
tunnusT
Topic thumbnail image
Multi-System Reactor
Reactor Build 26284 stuck at Loading Reactor UI
T
Topic thumbnail image
Multi-System Reactor
MSR with reverse proxy
tunnusT
I'm trying to use MSR via reserve proxy in Synology DSM, but MSR page does not load https://<public ip>:30000/reactor/en-US/ At the same time logging page loads normally https://<public ip>:30000/api/v1/log I thought maybe authentication was messing it up, but there was no deny entries in the log, and also disabling authentication did not make any difference. For this use case VPN is not an option (that works, but as said not an option for this particular use case). Any ideas what could cause this? MSR build latest-26242-28d69aa8, Chrome browser
Multi-System Reactor
Missing attribute after upgrade
3
Topic thumbnail image
Multi-System Reactor
[MSR] Native fan capabilty
therealdbT
Nothing more to add. I see we have hvac_blower, but, anyway, maybe a native fan on the same assumptions of the fan from HASS could be reasonable. I have a couple of them. ie, this is from ESPHome via HASS. x_hass.domain="fan" x_hass.entity_id="fan.kitchen_seashell_hood_ventilation_fan" x_hass.floor_id=null x_hass.services=["fan","esphome"] x_hass.source="esphome" x_hass.state="off" x_hass_attr.friendly_name="Seashell Hood Ventilation Fan" x_hass_attr.percentage=50 x_hass_attr.percentage_step=25 x_hass_attr.preset_mode="" x_hass_attr.preset_modes=[] x_hass_attr.supported_features=49 Thanks.
Multi-System Reactor
[MSR] Rule do not fire
therealdbT
Topic thumbnail image
Multi-System Reactor
Rule condition shows TRUE in UI but Rule never transitions to SET — survives full restart
N
Build: latest-26221-b25bb3e3, Docker on Synology. Hi, I have a Rule whose Trigger/Constraints reference other Rules via Rule State ... is TRUE. At some point it stops firing. Expanding the rule's condition tree in the UI shows every Trigger and Constraint condition green/TRUE — confirmed live by walking into the room and watching Motion go true in real time. Rule History shows no new SET, just old reset entries. Tried, on the same rule, same evening: recreating the trigger conditions with fresh IDs, recreating the constraint conditions with fresh IDs (flat and wrapped in a new Group — wrapping in a Group produced one SET, but it didn't reproduce on repeat attempts with the same structure), and finally a full container restart with a verified-correct saved rule. Still no SET, even with a fresh live motion event right after the restart. Separately, I found that this rule (and its 10 per-room clones) share identical internal condition/group IDs with each other — leftover from a batch clone done months ago, never regenerated. Not sure if that's related, since fixing the IDs didn't reliably fix the symptom either. Has anyone seen a Rule State condition show TRUE in the UI without the Rule ever producing a SET, surviving a clean restart? Thanks in advance
Multi-System Reactor
DynamicGroupController and attributes
therealdbT
Hey @toggledbits I'm back to trying to optimize a couple of things based on dynamic group. First of all, I think I found a typo in the doc: primary_attribute: "binary_sensor.state" primary_attribute_value: | d = false; each id in members: d = getEntity(id)?.attributes?.power_switch?.state or d, d I think the correct code snippet is d = false, All that said, my use case for dynamic groups is to group 3 different climate devices, so I could easily command them at the same time. Commands are good, but sometimes I want to check if any of the devices are on, and that's easily done with a similar snippet as the one you have in the docs. But this is limited to the primary attribute, while I want to have any of the attributes in the group to be driven by a similar logic (while all are null in the group). ie, access hvac_control.mode and see if any of the unit is set to cool, or heat. Is that possible, without re-defining an expression in each of my rules? Thanks!
Multi-System Reactor
Unofficial thread for compatibility
tunnusT
As there are statements about compatibility for home assistant versions in MSR new version announcements (e.g. "HassController: Bless Hass to 2025.7.3"), I thought it would be good idea to track other controllers as well. As an example, I can confirm that build "latest-25208-c53e8513" works with Hubitat Elevation C-8 platform version 2.4.2.134 using Maker API. Updates: (the latest versions first in the list) OK: build "latest-25264-2fbe9217" with Hubitat C-8 platform v. 2.4.3.123
Multi-System Reactor
Ooops - Deleted Reactor Ex Machina II
R
I accidentally deleted Reactor Ex Machina II (REM II) from my Reactor rules. I tried to recover it by deleting the .json and .dval in the Rules subdirectory and then recreating it from Togglebits original posting, but that did not work. Does anyone know how to recover REM ll ?
Multi-System Reactor
Bail out of failed reaction?
T
Topic thumbnail image
Multi-System Reactor
Arming Envisalink panel from MSR
T
Topic thumbnail image
Multi-System Reactor
[Solved] DynamicGroupController updating members issue
CrilleC
Edit: Solved in latest-26221. Bare-metal latest-26193 I have this group: "OKforLarm": name: OK för Larm select: - include_controller: vera - include_capability: door_sensor filter_expression: entity.attributes.door_sensor.state It contains the entities I expect but behaves a bit odd. When I open vera>device_10097 the entity attribute door_sensor.state changes to true but it won't show up as member in the group, when I also open vera>device_10095 they both shows as members and when I close vera>device_10095 it disappear from the group but when I close vera>device_10097 it lingers in the group until I restart Reactor.
Multi-System Reactor

sunset/sunrise question in 22251

Scheduled Pinned Locked Moved Multi-System Reactor
11 Posts 2 Posters 1.7k Views 2 Watching
  • 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.
  • G Offline
    G Offline
    gwp1
    wrote on last edited by gwp1
    #1

    Been fighting with my Day/Evening/Night modes of late. Thought I had them working just right but after deploying 22251 yesterday evening something "happened." (Note, I've been holding off on reporting what I think is a bug using the sunrise/sunset settings in rules wherein they won't hold a setting until I destroy and recreate that criteria a second time.)

    My rulesets:

    1ceeb3f8-4549-409b-82dc-99da5b9f4aef-image.png

    ccb90573-a0f7-4d9e-9ccf-2ed74c4d63ec-image.png

    I had to one-eyed add the mode restrictions at midnight after being awakened from a sound sleep.

    I'm trying to keep my rules slim/trim after finding many duplicate/conflicting rulesets during a review over the past few days.

    For Days, I should be present, it should start at 0630 ET each weekday, 0730 ET each weekend day (as sunrise often comes after those times.) No concerns about crossing the "midnight divide" with day.

    For Evenings, I should be present, it should start at sunset and end at sunrise (note: that sunrise thing won't ever happen as one goes to bed at SOME point and invokes night) but I do have the logic in there so the system doesn't switch to day or just get lost at midnight if I'm up late.

    Any thoughts on how to make this cleaner but not be awakened at midnight? lol

    *Hubitat C-7 2.5.2.139
    *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

    *HAOS
    Core 2026.10.4
    w/ HA Connect ZWA-2 & ZBT-2
    FW: v1.1
    SDK: v7.23.1

    *Prod MSR in docker/portainer
    MSR: latest-26298-fbb75fb8
    MQTTController: 25139
    ZWave Controller: 25139

    1 Reply Last reply
    0
    • toggledbitsT Online
      toggledbitsT Online
      toggledbits
      wrote on last edited by toggledbits
      #2

      In your Day rule, you have "before sunset" as a condition. That means the test will be true from midnight to sunset, false from sunset to midnight, and then go back to true at midnight, every day. Is that consistent with your intentions? IMO, Day isn't day until after sunrise (i.e. the period between midnight and sunrise isn't Day, it's part of Night to my thinking).

      Oh, and in Evening, your two conditions "after sunset" OR "before sunrise" can be written as a single condition "between sunset and sunrise".

      Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

      G 1 Reply Last reply
      0
      • toggledbitsT toggledbits

        In your Day rule, you have "before sunset" as a condition. That means the test will be true from midnight to sunset, false from sunset to midnight, and then go back to true at midnight, every day. Is that consistent with your intentions? IMO, Day isn't day until after sunrise (i.e. the period between midnight and sunrise isn't Day, it's part of Night to my thinking).

        Oh, and in Evening, your two conditions "after sunset" OR "before sunrise" can be written as a single condition "between sunset and sunrise".

        G Offline
        G Offline
        gwp1
        wrote on last edited by
        #3

        @toggledbits For Days the issue is that sunrise often comes after alarm times. Would "after sunrise" or "when alarm times is true" better address?

        Re Evenings, I wasn't sure with the midnight crossover that the "between" would address the needs.

        *Hubitat C-7 2.5.2.139
        *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

        *HAOS
        Core 2026.10.4
        w/ HA Connect ZWA-2 & ZBT-2
        FW: v1.1
        SDK: v7.23.1

        *Prod MSR in docker/portainer
        MSR: latest-26298-fbb75fb8
        MQTTController: 25139
        ZWave Controller: 25139

        toggledbitsT 1 Reply Last reply
        0
        • G gwp1

          @toggledbits For Days the issue is that sunrise often comes after alarm times. Would "after sunrise" or "when alarm times is true" better address?

          Re Evenings, I wasn't sure with the midnight crossover that the "between" would address the needs.

          toggledbitsT Online
          toggledbitsT Online
          toggledbits
          wrote on last edited by
          #4

          @gwp1 said in sunset/sunrise question in 22251:

          For Days the issue is that sunrise often comes after alarm times. Would "after sunrise" or "when alarm times is true" better address?

          I can't really answer this, not knowing enough about your rules and how Alarm Times works. I'll leave it to your experimentation, I just wanted to point out that there's a significant number of hours that may not comport with your intentions.

          @gwp1 said in sunset/sunrise question in 22251:

          Re Evenings, I wasn't sure with the midnight crossover that the "between" would address the needs.

          Very important feature that it handles midnight crossing correctly on all time conditions.

          Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

          G 1 Reply Last reply
          0
          • toggledbitsT toggledbits

            @gwp1 said in sunset/sunrise question in 22251:

            For Days the issue is that sunrise often comes after alarm times. Would "after sunrise" or "when alarm times is true" better address?

            I can't really answer this, not knowing enough about your rules and how Alarm Times works. I'll leave it to your experimentation, I just wanted to point out that there's a significant number of hours that may not comport with your intentions.

            @gwp1 said in sunset/sunrise question in 22251:

            Re Evenings, I wasn't sure with the midnight crossover that the "between" would address the needs.

            Very important feature that it handles midnight crossing correctly on all time conditions.

            G Offline
            G Offline
            gwp1
            wrote on last edited by gwp1
            #5

            @toggledbits Ok, this has surfaced the potential bug I referenced in my OP.

            I'm attempting to edit the Evening ruleset to change to "between sunset and sunrise". I add the trigger:

            f76a4cf3-e4f6-44e5-a789-ae1bbc8af895-image.png

            I click save and exit

            989272a0-82d7-4649-b2d2-0b6cd0020371-image.png

            Rule shows as SET

            747c65be-40ba-4841-89cc-fb5f640e6b4f-image.png

            The trigger has changed to "from sunrise to sunset"

            c84953eb-6df0-41d2-9413-973c372d75f7-image.png

            And now my system is fighting over Day vs Evening.

            EDIT:
            Further, editing the trigger does not prompt for save - it's as though the change in the trigger isn't seen.

            c1f417a4-5caa-44be-9ffa-1573d7d09a81-image.png

            12afa669-34ed-4f82-b76f-837f18966755-image.png

            Further testing... adding a new trigger of "after sunset" and clicking save switches to "after sunrise".

            *Hubitat C-7 2.5.2.139
            *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

            *HAOS
            Core 2026.10.4
            w/ HA Connect ZWA-2 & ZBT-2
            FW: v1.1
            SDK: v7.23.1

            *Prod MSR in docker/portainer
            MSR: latest-26298-fbb75fb8
            MQTTController: 25139
            ZWave Controller: 25139

            G 1 Reply Last reply
            0
            • G gwp1

              @toggledbits Ok, this has surfaced the potential bug I referenced in my OP.

              I'm attempting to edit the Evening ruleset to change to "between sunset and sunrise". I add the trigger:

              f76a4cf3-e4f6-44e5-a789-ae1bbc8af895-image.png

              I click save and exit

              989272a0-82d7-4649-b2d2-0b6cd0020371-image.png

              Rule shows as SET

              747c65be-40ba-4841-89cc-fb5f640e6b4f-image.png

              The trigger has changed to "from sunrise to sunset"

              c84953eb-6df0-41d2-9413-973c372d75f7-image.png

              And now my system is fighting over Day vs Evening.

              EDIT:
              Further, editing the trigger does not prompt for save - it's as though the change in the trigger isn't seen.

              c1f417a4-5caa-44be-9ffa-1573d7d09a81-image.png

              12afa669-34ed-4f82-b76f-837f18966755-image.png

              Further testing... adding a new trigger of "after sunset" and clicking save switches to "after sunrise".

              G Offline
              G Offline
              gwp1
              wrote on last edited by
              #6

              Opened a bug on this issue.

              *Hubitat C-7 2.5.2.139
              *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

              *HAOS
              Core 2026.10.4
              w/ HA Connect ZWA-2 & ZBT-2
              FW: v1.1
              SDK: v7.23.1

              *Prod MSR in docker/portainer
              MSR: latest-26298-fbb75fb8
              MQTTController: 25139
              ZWave Controller: 25139

              1 Reply Last reply
              0
              • toggledbitsT Online
                toggledbitsT Online
                toggledbits
                wrote on last edited by
                #7

                OK. I would have liked to see a bit more concise description in that OP (e.g. "sunrise/sunset selections not saving when edited"), but found and fixed. Another thing you might have observed is when you changed those menus to sunset first and sunrise second, you didn't get the green bar on the left of the condition, indicating that it had been changed.

                I'll do a build later today with the fix. In the meanwhile, you can work around it by changing the sunrise/sunset start and end to what you want, then edit the offset to something and then re-edit and put it back to 0 (or whatever you want). You should get a green bar on the left side of the condition when you do that.

                Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                G 1 Reply Last reply
                0
                • toggledbitsT toggledbits

                  OK. I would have liked to see a bit more concise description in that OP (e.g. "sunrise/sunset selections not saving when edited"), but found and fixed. Another thing you might have observed is when you changed those menus to sunset first and sunrise second, you didn't get the green bar on the left of the condition, indicating that it had been changed.

                  I'll do a build later today with the fix. In the meanwhile, you can work around it by changing the sunrise/sunset start and end to what you want, then edit the offset to something and then re-edit and put it back to 0 (or whatever you want). You should get a green bar on the left side of the condition when you do that.

                  G Offline
                  G Offline
                  gwp1
                  wrote on last edited by gwp1
                  #8

                  @toggledbits My screenshots were a step-by-step thru the issue. "I click save and exit "does show that there is no green bar next to the edited trigger.

                  *Hubitat C-7 2.5.2.139
                  *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                  *HAOS
                  Core 2026.10.4
                  w/ HA Connect ZWA-2 & ZBT-2
                  FW: v1.1
                  SDK: v7.23.1

                  *Prod MSR in docker/portainer
                  MSR: latest-26298-fbb75fb8
                  MQTTController: 25139
                  ZWave Controller: 25139

                  G 1 Reply Last reply
                  0
                  • toggledbitsT Online
                    toggledbitsT Online
                    toggledbits
                    wrote on last edited by
                    #9

                    Yes, I could see that. I was referring to the OP, which you also made reference to. Fixed now. Build coming later.

                    Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                    G 1 Reply Last reply
                    1
                    • G gwp1

                      @toggledbits My screenshots were a step-by-step thru the issue. "I click save and exit "does show that there is no green bar next to the edited trigger.

                      G Offline
                      G Offline
                      gwp1
                      wrote on last edited by
                      #10

                      Can confirm that adding a new trigger and changing to 1 minute after for each end of it is a successful workaround.

                      b951322c-265b-47d6-8a61-fa59dced6a89-image.png

                      *Hubitat C-7 2.5.2.139
                      *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                      *HAOS
                      Core 2026.10.4
                      w/ HA Connect ZWA-2 & ZBT-2
                      FW: v1.1
                      SDK: v7.23.1

                      *Prod MSR in docker/portainer
                      MSR: latest-26298-fbb75fb8
                      MQTTController: 25139
                      ZWave Controller: 25139

                      1 Reply Last reply
                      0
                      • toggledbitsT toggledbits

                        Yes, I could see that. I was referring to the OP, which you also made reference to. Fixed now. Build coming later.

                        G Offline
                        G Offline
                        gwp1
                        wrote on last edited by
                        #11

                        @toggledbits I wasn't sure at the time of the OP post that it was a legit bug and not just... me.

                        🙂

                        *Hubitat C-7 2.5.2.139
                        *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                        *HAOS
                        Core 2026.10.4
                        w/ HA Connect ZWA-2 & ZBT-2
                        FW: v1.1
                        SDK: v7.23.1

                        *Prod MSR in docker/portainer
                        MSR: latest-26298-fbb75fb8
                        MQTTController: 25139
                        ZWave Controller: 25139

                        1 Reply Last reply
                        0
                        • toggledbitsT toggledbits locked this topic on
                        Reply
                        • Reply as topic
                        Log in to reply
                        • Oldest to Newest
                        • Newest to Oldest
                        • Most Votes


                        Recent Topics

                        • UI not loading after upgrading to 26318
                          toggledbitsT
                          toggledbits
                          0
                          6
                          158

                        • [Resolved] Hubitat upgrade 2.5.3.123 may have broken login
                          toggledbitsT
                          toggledbits
                          0
                          8
                          307

                        • Reactor (Multi-System/Multi-Hub) Announcements
                          toggledbitsT
                          toggledbits
                          5
                          153
                          163.7k

                        • Reactor Inspect - a small read-only helper panel for MSR
                          G
                          gwp1
                          2
                          8
                          628

                        • Reverse proxy & API ACL
                          tunnusT
                          tunnus
                          0
                          9
                          539

                        • MFA
                          T
                          tamorgen
                          0
                          28
                          1.5k

                        • Grouped devices
                          G
                          gwp1
                          0
                          3
                          205

                        • Login protections
                          toggledbitsT
                          toggledbits
                          0
                          2
                          244

                        • Reactor Build 26284 stuck at Loading Reactor UI
                          T
                          tamorgen
                          0
                          16
                          1.8k

                        • MSR with reverse proxy
                          tunnusT
                          tunnus
                          0
                          12
                          914

                        • Missing attribute after upgrade
                          3
                          3rdStng
                          0
                          3
                          701

                        • Use of Google Gemini as an MSR and Hubitat configuration aid
                          therealdbT
                          therealdb
                          0
                          2
                          340
                        Powered by NodeBB | Contributors
                        Hosted freely by 10RUPTiV - Solutions Technologiques | Contact us
                        • Login

                        • Don't have an account? Register

                        • Login or register to search.
                        • First post
                          Last post
                        0
                        • Categories
                        • Recent
                        • Tags
                        • Popular
                        • Unsolved