Denied: Whonix.Newstatus+status from qube to sys-whonix

So, I am having some trouble getting both Kick and Tor to behave with Whonix. Neither seems to be working. Tor for some reason thinks it’s tomorrow.

Aug 31 00:33… [notice] New control connection opened.

While its sun 30th of august according to my local machine. I assume it is giving me universal time. It seems to work with some sites but I always get a big Nada from others. It works then it dose not. So, when I use the Tor browser over who-nix it always drops this in the logs

Aug 31 00:31… [warn] Not attempting connection to [scrubbed]:80 because the network would reject it. Are you trying to send Tor traffic over Tor? This traffic can be harmful to the Tor network. If you really need it, try using a bridge as a workaround.

Is making the other Qubes work as simple as hooking it to the sys firewall rather than whonix?

If Tor is built in on who-nix we don’t need the tor browser right. There should be at least a note in the Qube templates. Warning me that this stacking the protocols thing can be a problem. Frankly I always thought who-nix used something else. This brings me to another thought why not some of the other privacy networks. Any way hope this helps some one.

Kicksecure and Tor Browser through Whonix-Gateway?
Please kindly don’t abbreviate these because that causes confusion.

Unsupported.

Whonix is based on Kicksecure . Typically there is no need to use Kicksecure through Whonix-Gateway.

Discouraged. → Refrain from “Tor over Tor” Scenarios.

Tor Browser should be used. See: Other Browsers

Related: Anonymize Other Operating Systems

Ok so that answers the main question Whonix is like ok I want to use tor let me point any cube at the whonix gateway bam I am anon.

This I don’t understand because then I will get a tor over tor error, as mentioned. Maybe there is a setting in the tor browser I have wrong? Maybe you can point me to that. I am doing some extra reading in the links you gave, still thanks for the reply